Aider edits your repo from the terminal. Aura decides what is allowed to land.
Aider is a command-line pair programmer that maps your repository, edits files in place and commits as it goes. It is open source, model-agnostic and one of the oldest tools in this category. Aura sits underneath it: same Git, same repo, but it reads each commit at the AST level, records why it happened, and refuses the ones that do not match what was asked.
What each one is for
What Aider is great at
- Repository awareness
The repo map is still one of the better answers to "how does an agent know what exists" without burning the whole context window.
- Model-agnostic
Anthropic, OpenAI, local models through Ollama — Aider has never tied you to one provider.
- Commits as it works
Every edit is a real Git commit, which makes undoing a step trivial and keeps history honest about what the agent touched.
- Open source, no app
A Python package and a terminal. Nothing to install beyond what you already have.
What Aura adds on top
- A check on those commits
Aider commits eagerly, which is good. Aura reads what the commit actually changed at the function level and compares it with the intent that was recorded for it.
- A deletion guard
"Clean up unused code" is the prompt that costs people a production incident. Aura names the exported function that went missing and traces its callers before the commit lands.
- Every other engine too
Aider is one engine. Aura drives Claude Code, Gemini CLI, Codex, Cursor Agents, Kimi, OpenCode and Aider from one composer on one history.
- A team plane
Symbol claims, a collision radar, cross-branch impact alerts. Aider is a single-developer tool by design.
Dimension by dimension
Side by side
When to pick which
Pick Aider if…
- You want the smallest possible agent that edits code and commits it.
- You are running a local model and want nothing between you and it.
Pick Aura if…
- Aider is committing faster than you can review.
- You need to explain a change to someone who was not there.
- More than one agent, or more than one person, works on this repo.
Keep Aider. Add the control layer.
Aider is one of the engines Aura drives, and even outside Aura the CLI hooks catch Aider commits: install aura, run aura init, and every commit Aider makes goes through the intent check and the deletion guard.
Aura & Aider
Does Aura replace Aider?
No. Aura drives Aider as one engine among several, and its commit hooks work on Aider commits whether or not you launch it from Aura.
Will Aura fight with Aider’s auto-commit?
No. Aura reads commits rather than owning them. The hook runs at commit time, checks the AST change against the recorded intent, and either passes or names the problem.
Ship with proof, not hope
Free public beta for macOS and Linux. Point it at a repo and keep driving Aider, now with a semantic diff, a verdict and a record on every change.