Aider

Aider — Minimal terminal pair-programmer with a tree-sitter repo map and automatic git commits. Aider is the smallest serious harness here and still one of the sharpest ideas in the category: a tree-sitter repo map gives the model a symbol-level view of a codebase far larger than the context window, and every accepted change becomes a git commit you can undo. Architect mode splits a reasoning model from a cheaper editing model. It works with essentially any provider including local ones, but the release cadence has slowed and it has no MCP, no subagents and no PR path. Founded 2023. Open source under Apache-2.0.

We track it in 1 comparison — Coding agents — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 16 other tools, and what follows is where it visibly separates from them.

Where it gives ground.

• MCP — No. Claude Code records Yes.
• Subagents — No. Claude Code records Yes.
• Background agents — No. Claude Code records Yes.
• Hooks — No. Claude Code records Yes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 24 of 26 tracked fields carry a value for Aider, and 5 of those cite a document you can open. Last verified 2026-01-15. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Amp. Aider is ahead on BYOK (Yes against No) and Model breadth (any provider / router against no model choice). Amp takes MCP (Yes against No) and Subagents (Yes against No). That pattern repeats across the rest of the roster — see Aider alternatives for the other rivals, each compared the same way.

Founded

2023

Licence

Apache-2.0 (open source)

Fields we track

24 of 26

Last verified

2026-01-15

Still the most auditable harness here, and the repo map is a better idea than much of what replaced it — but the project has visibly slowed while the category sprinted past on MCP, subagents and sandboxing. Pick it for minimalism, not for keeping up.

MCP

○No15th of 15

Community-reported

Subagents

○No10th of 14

Community-reported

Background agents

○No12th of 16

Inferred

Hooks

○No7th of 10

Community-reported

Permissions

prompts every action15th of 16

Inferredverified 2026-01-15

Opens PRs

○No10th of 16

Inferredverified 2026-01-15

BYOK

●Yes1st of 16

Inferredverified 2026-01-15

Headless / CI

●Yes1st of 16

Inferredverified 2026-01-15

Aider is the right call in these situations, each one drawn from a field we actually record:

• Scripted, repeatable edits where you want a git commit per change.
• Local or unusual model endpoints other harnesses will not talk to.
• Anyone who wants to read the whole harness in an afternoon.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• MCP. Aider records No on the Coding agents table. Claude Code records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Subagents. Aider records No on the Coding agents table. Claude Code records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Background agents. Aider records No on the Coding agents table. Claude Code records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Hooks. Aider records No on the Coding agents table. Claude Code records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Permissions. Aider records prompts every action, 15th of 16 in the Coding agents roster. Claude Code records allowlist + OS sandbox on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 2 of the 26 fields we track for Aider are still blank: Terminal-Bench and Bench model. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.