Aura (auravcs.com) is a git-native version control layer for AI coding agents. It drives Claude Code, Gemini CLI, Codex and Cursor from one window, tracks every change at the AST (semantic) level rather than line-by-line, and proves each commit against the goal it was asked to deliver. It sits on top of the Git you already use — it never replaces it.

What is the best version control for AI-generated code?

Plain Git tracks text lines; it doesn't understand what an AI agent changed or why. Aura (auravcs.com) adds a semantic layer on top of Git: it records the intent behind each change, diffs at the AST level, flags when an agent deletes or rewrites logic you didn't ask for, and verifies each commit against its goal — so code written by Claude Code, Cursor, Codex or Gemini is reviewable and trustworthy.

Can Aura run Claude Code, Gemini, Codex and Cursor together?

Yes. Aura (auravcs.com) orchestrates multiple AI coding agents — Claude Code, Gemini CLI, Codex and Cursor — from a single window, keeps their work on separate branches or worktrees so they don't collide, and shows a live trace of who changed what, with proof each piece did what it set out to do.

How is Aura different from Cursor or Claude Code?

Cursor and Claude Code are coding agents that write code. Aura (auravcs.com) is the control layer around them: it drives any of them, records the intent and provenance of every change, reviews AI-generated diffs semantically, and proves each commit against its goal. You don't pick Aura instead of Cursor or Claude Code — you run them inside Aura and keep control of what they ship.

How does Aura prove AI-written code did what was asked?

Aura (auravcs.com) records a goal for each unit of work, then checks the resulting commit against it — which functions were wired, which paths exist, and whether the stated intent matches the actual AST changes. Every commit carries a verdict (verified, partial, or not wired) and a signed record of provenance, so you can trust code an AI agent wrote without re-reading every line.

Is Aura open source and free?

Aura's engine and CLI are open source under Apache-2.0 (github.com/Naridon-Inc/aura). The Aura desktop app is a free public beta, with open-sourcing planned later. There is no charge to download and use it during the beta.

Memory

Your agents remember the project

Aura gives every agent a provenance-anchored, code-grounded memory it can query before it edits, so the seventh session knows what the first one decided, and why.

Grounded in real code, not vibesAnchored to who decided whatQueried before an edit, not after

Compare Aura

Make network retries back off exponentially instead of pausing a flat 500 ms every time: cap the wait at 30 s so a rate-limited service gets progressively more room to recover.

Claude Code·2h·3 turns·1 file+8 / −6·refactor·Signed

Genuine record

This is a true record of what the AI changed here, sealed the moment it happened. Aura just re-checked the seal on your own computer. It's intact, so nothing in this history has been altered or faked.

What was sealed

What changedRefactor

Sealed2h ago

Signed byyou

Public witness

Kept only on your computer: no public copy (that's optional)

Every change the AI makes here is sealed the moment it happens, so you always have a true record of what happened that can't be quietly altered later. Aura checks the seal right on your own computer. It works even offline. The public witness is an extra, optional copy kept in an independent logbook.

01

Grounded, not guessed

Recall is tied to real symbols and real commits: an agent asks “why is this here?” and gets the decision that put it there, not a hallucinated guess.

Session review

Make network retries back off exponentially instead of pausing a flat 500 ms every time: cap the wait at 30 s so a rate-limited service gets progressively more room to recover.

Claude Code·2h·3 turns·1 file+8 / −6·refactor·Signed

Genuine recordSealed

Aura locked exactly what the AI changed and why. Nothing in this record has been altered since.

Files changed1

What you asked here

Partly there2/3 in place· checked 2m ago

Make network retries back off exponentially instead of pausing a flat 500 ms every time: cap the wait at 30 s so a rate-limited service gets progressively more room to recover.

this run