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.

Command line · Apache-2.0 engine

The whole engine, from your terminal.

One Rust binary grafts onto the Git you already have: no migration. Drive every coding agent on one semantic engine, prove what each one changed, and surgically undo the rest. The same engine the desktop app runs on, scriptable from any shell.

$curl -fsSL https://auravcs.com/install.sh | bash

View on GitHub Command reference

macOS · Linux·11 languages, AST-level·fully open source

One engine for the agents your team already uses

ClaudeGeminiAntigravityCursorCodexOpen CodeKimiPiAny MCP agent

What it does

Six verbs that keep agents honest

Drive every agent

Run Claude Code, Gemini, Codex, Cursor and more on one engine, with one shared history: switch brain mid-thread without losing the thread.

$ aura handover --agent claude

Hand it a backlog

Crew is the work-loop: agents claim unblocked tasks in their own worktrees and prove each goal before it merges. The same loop runs from chat with /loop.

$ aura loop run

Prove a change works

Trace the logic paths in the AST graph and get a verdict (wired, partially wired, or not at all) tied to the goal it was meant to deliver.

$ aura prove --goal "…"

Read what really changed

A semantic review at the logic level, with risk scoring and AST-anchored inline comments, not just a wall of red and green.

$ aura pr-review --base main

Undo one mistake, surgically

Revert a single function or class to its last safe state at the AST level: zero merge conflicts, the good code untouched.

$ aura rewind <fn> <file>

Trace who wrote it, and why

git blame → checkpoint → agent session → transcript. See the exact reasoning that produced any line of code.

$ aura explain <fn> <file>

Live in minutes

Point it at a repo. Keep your workflow.

Install, run aura enable inside any Git repository, and Aura wires the hooks and the MCP server. Commit, push and branch exactly as before: Aura tracks the logic underneath and steps in only when an agent's change doesn't match its stated intent.

No new remoteNo lock-inWalk away to plain git anytime

aura: zsh

~/tasks $ aura enable

hooks installed · MCP server registered · watcher live

~/tasks $ aura status

1,284 logic nodes tracked · strict mode OFF · session active

~/tasks $ aura prove --goal "checkout requires auth"

verified · 3/3 paths wired

~/tasks $ aura rewind charge() src/pay.rs

reverted one function to its last safe state

The reference