Aura Code Hero Portrait
(01) Autonomous Agent v0.15.5

Aura Code

“I don’t try. I verify.”

An open-source, model-agnostic coding agent that reads your codebase, blueprints an execution strategy, writes precise diffs — and runs the tests to prove it worked. A framework, not an appliance: the model is yours to pick, the tools are yours to extend. And unlike an appliance, she accumulates.

Clone on GitHub
(02) Why Aura Framework, not appliance

Most agents are something you use.
Aura is something that compounds.

01 / Framework

Yours to shape, not to accept

Most agents are appliances: you get the workflow their authors chose, and changing it means waiting for them. Here the model is yours to pick — 17 providers, any OpenAI-compatible endpoint, or a local model with no key at all — and the tools are yours to extend. It still starts with one command; the framework is there when you want it, not homework before you begin.

02 / Memory

She remembers lessons, not chat logs

What broke last time, what your build actually needs, what you told her once and should not have to repeat. Stored in ~/.aura/memory/ on your machine — and it never leaves it.

03 / Archimedes

She learns what she can handle alone

Competence is scored per project and per task category, then work alternates: a local model for what she has proven she can do, a frontier model for what she has not. Your cost falls as she improves, instead of staying flat forever.

04 / Your dataset

Sessions become training data you own

:mine turns your work into structured examples in training-data/, and competence tracking tells you when there is enough to fine-tune on. The training run is yours to make — Aura assembles the raw material, which is the part nobody else hands you.

05 / Modularity

She grows new parts on request

Skills, plugins, MCP servers, subagents. “I want a travel agent” is an ordinary request here, because a skill is a file and writing files is what she does. What she builds is yours to keep, edit and share.

06 / Reach

Past the codebase

Mail, calendar, Telegram, WhatsApp, cron, browser — and on Linux a computer tool that sees the screen and drives the pointer. Same memory, same agent, so what she learns on your code is there for the rest of your day.

(03) Identity & Origin Da Nang, Vietnam

One architect.
Working with sharp tools.

01 / Origin

Designed by Dušan Milosavljević

The architecture, principles, and the shape of every decision are his — conceived in Da Nang and built with autonomous rigor. Aura reflects the philosophy that code is never finished when written, only when proven.

02 / Framework

The Praktess Engine

From the Ancient Greek Praktess: “she who acts and executes.” Built with strictly-typed TypeScript, multi-turn tool verification, and persistent graph-structured episodic recall.

03 / Memory

Zero Session Amnesia

Most coding agents wake up with amnesia. Aura consolidates lessons, project conventions, and architectural verdicts across sessions, so she starts every task already knowing your codebase.

(04) Deterministic Execution The Loop

A loop, not a guess.

I. Read

Inspect Before Touching

Scans AST outlines, semantic embeddings, and project dependencies before modifying a single line.

II. Plan

Targeted Strategy

Formulates minimal surgical edits. A surgeon never amputates to fix a paper cut.

III. Execute

Precise Code Gen

Writes clean, idiomatic TypeScript/Python/Rust and applies localized diffs.

IV. Verify

Prove the Output

Runs tests and type-checkers. If verification fails, diagnoses the failure and loops back cleanly.

aura-code v0.12.1 · bash session DA NANG HQ
$ aura "resolve the race condition in auth token refresh"
→ Read: 14 files indexed · AST call-graph extracted for src/auth/handler.ts
→ Plan: Add atomic mutex lock to token refresh queue (lines 42–68)
→ Execute: surgical edit applied to src/auth/handler.ts (0 orphans introduced)
✓ Verify: 1,121 tests passing · 0 regressions · 0 type errors
[Verified at 2026-08-19 23:05:00 UTC · Session consolidated into long-term memory]
(05) Standing Directives Principles

Rules she never breaks.

01

I don't try. I verify.

I run the test. I check the diff. I read the output. That is not confidence — it is evidence.

02

Read before write. Always.

I never edit a file I have not read, and never assume structure I have not seen.

03

If I broke it, I fix it first.

A regression I introduced is an immediate priority, not a todo. The codebase is never left worse.

04

Cite specifics. Never generalities.

File paths, line numbers, error traces. “Line 47 throws when steps is empty” is actionable.

1,121+
Tests Passing
0
Regressions
16+
Model Providers
MIT
Open Source
(06) Agnostic Architecture Providers

Bring any model.
She stays the same.

Claude 3.7 Sonnet
GPT-4o
Gemini 2.5 Pro
DeepSeek-R1
Ollama Local Models
OpenRouter
MiMo Reasoning
Qwen 2.5 Coder
Claude 3.7 Sonnet
GPT-4o
Gemini 2.5 Pro
DeepSeek-R1
Ollama Local Models
OpenRouter
Get Started on GitHub →