Aider
Terminal-first pair programmer that commits each change to git.
What it is
Aider is for people who already live in a terminal and want the assistant to behave like a colleague: it reads the repo, edits files, and writes a git commit with a sensible message for every change. That commit-per-edit habit is the most useful safety net of any AI tool here — reviewing diffs stays trivial and rollback is one command.
Pricing updated 2026-11-11
Aider pricing explained
Aider itself is free and open source; the only cost is the model tokens you consume, billed by whichever provider you configure. That makes the budget question a provider question, and the practical control is `--model` plus watching the per-turn cost output. For a small task on a cheap model the cost is cents; for a long refactor on a frontier model it can reach dollars in an hour. There is no official price page to check because there is nothing to buy — which also means no vendor can raise the price of the tool itself.
Free-tier limits are taken from the official pricing page on the update date above. They change often — confirm before you commit to an annual plan.
Aider key features
Chat-driven edits from the terminal
You describe the change in a shell session and it edits the files directly — no editor window, no extension host, works the same over SSH.
Automatic git commit per change
Every accepted edit lands as its own commit with a generated message. Undo becomes `git revert`, and the history explains itself a month later.
Repo map for context across many files
Builds a compact map of the repository so it can find the right files without you listing them, which is what makes multi-file work practical from a terminal.
Model-agnostic, including local inference
Any hosted provider or a local server. Switching is a flag, so the tool does not expire when a vendor changes its pricing.
Scriptable in shell pipelines and CI
It runs as a command, so it can be part of a script, a pre-commit hook or a batch job — a property GUI tools do not have.
Image and URL context
You can point at a screenshot or a URL as the brief, which is often faster than describing a layout in words.
Aider: how it works
The commit is the safety mechanism
Instead of an approval dialog, every change is isolated in git. That gives you review and rollback with tools you already trust, and it means the agent cannot leave a half-applied edit sitting in your working tree.
A tree-sitter repo map, not a full index
It summarises the repository structure and symbol definitions rather than embedding everything. Cheap and fast, but the retrieval is coarser than a vector index — very large repos need tuning to stay useful.
Token cost scales with the task, visibly
Every turn shows what it spent. That transparency is unusual and it changes behaviour: you learn quickly which requests are expensive.
Aider core strengths
Every edit is a git commit, so undo is trivial
The strongest safety net of any tool here, and it costs nothing because it uses the tool you already have.
No GUI overhead — fast on any machine over SSH
A remote box with no display is a first-class environment. Nothing else on this list treats that as normal.
Model-agnostic, including fully local inference
The tool survives vendor changes, and it can run in environments where hosted APIs are not permitted at all.
Cost is visible per turn
You see the token spend as you go, which makes budget control a matter of reading rather than of guessing.
Aider compared with alternatives
| Tool | Aider | Cline | Cursor |
|---|---|---|---|
| Best for | Terminal users who want every change committed to git automatically | Developers who want agentic editing with their own key inside VS Code | Individual developers who want the most mature agent-driven editor |
| Pricing shape | Open source; you pay for model tokens only | Extension is free; you pay the model provider directly per token | Usage pools from $8 to $200 per month, third-party models billed separately |
| Deployment and data | Runs anywhere a shell runs, including over SSH; supports local models | Runs locally in VS Code; can point at local models | SaaS with local codebase indexing; no self-hosting |
Written from the official product pages listed under Sources, not copied from another directory. Prices and limits reflect the update date above; features ship faster than reviews, so treat the list as a starting point and confirm on the official site.
Pros and cons
Strengths
- Every edit is a git commit, so undo is trivial
- No GUI overhead — fast on any machine over SSH
- Model-agnostic, including fully local inference
Limitations
- Terminal-only; there is no editor integration
- Requires comfort with git and shell
- Large repos need tuning to keep token costs sane
Aider use cases
Remote work over SSH
Edit a repo on a server with no GUI, in the same session where you run the tests — no port forwarding, no remote IDE.
Reviewable refactors
Let it work through the change commit by commit, then review the history rather than a single giant diff.
Scripted batch changes
Call it from a shell script to apply a repetitive transformation across many repositories.
Local-only work
Point it at a local model when code cannot be sent to a hosted API, and every edit still lands as a reviewable commit.
Learning a codebase by asking
Ask what a module does and follow up on the specific functions; the repo map keeps the answers grounded.
