Pair programmer

Aider

Focused pair programming built around Git, diffs, and explicit control.

Status: Active
License: Apache-2.0
Evidence: Documented + code-verifiable, 18 sources
Product record checked: 2026-07-27

At a glance

A mature terminal pair-programming tool with broad model support, local endpoints, Git-backed undo, a repository map, scripting, and automatic lint, test, and commit workflows.

Good choice if

Developers who prefer a tight Git-centric editing loop
Pair programming with explicit files, diffs, lint, and test feedback
Model experimentation including local endpoints and Copilot access

Check before choosing

Aider edits and runs commands directly in the host workspace: it has no built-in OS or container sandbox, and --yes-always removes confirmation prompts
Git-backed /undo is strong file recovery but cannot reverse shell side effects, external services, or edits made outside Aider's commits
The browser surface is an experimental Streamlit UI and /web is page scraping, not an autonomous browser-control tool

See 4 more considerations

Watch-files is editor-agnostic integration rather than a maintained first-party IDE extension; the Python Coder API is explicitly unsupported
It is deliberately single-agent and does not provide native MCP or delegated subagents
The public release surfaces lag one another: GitHub Releases stops at v0.86.0 and the release-history page at v0.86.1, while the audited source commit explicitly bumps the package to v0.86.2
Its benchmark suite is project-owned and model-focused; HarnessMatch does not turn it into an independent product score

Quick facts

Interfaces: Terminal, IDE, Web, Automation
Approval style: Interactive approvals
Model portability: Provider + local
Isolation: No first-party isolation
Agent organization: Single-agent loop
Local model path: DocumentedThe source establishes the mechanism, not its quality or availability in every mode.

View full technical record

Catalog layer: Coding harness
Harness membership: Qualifies: 4 required criteria evidenced
Product role: Pair programmer
Agent organization: Single-agent loop
Runtime posture: Host-first
Isolation options: No first-party isolation
State model: Session-based
Context lifecycle: Managed context lifecycle
Permission posture: Interactive approvals
Verification: Tool-assisted checks
Observability: Session transcript
Recovery: File checkpoint
Interfaces: Terminal, IDE, Web, Automation
Provider posture: Multi-provider
Model portability: Provider + local
Subscription access: Available
Enterprise access: Not documented
Local model path: DocumentedThe source establishes the mechanism, not its quality or availability in every mode.
Claim boundary: Harness capability only

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP): Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Reusable skills: Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Local models: DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism: Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Runs without an open UI: DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control: Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution: Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Undo file changes: DocumentedProduct-supported file or session rollbackSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.

Getting started

Install Aider, configure a provider or local endpoint, and start it inside a Git repository.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit: Qualifies, 4/4 criteria
Operating model: 7/7 layers documented

Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced

Adaptive agent loop
Documented
The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.
EvidenceAider documentation
Repository tool execution
Documented
The system can use tools to inspect and change a repository or its execution environment.
EvidenceOptions reference
Task-aware context management
Documented
The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.
EvidenceRepository map
Model-independent runtime control
Documented
Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.
EvidenceOptions reference

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented

Execution & isolationHost processDocumented mechanism, not a performance score.
Tooling & integrationsBuilt-in toolsDocumented mechanism, not a performance score.
Context & stateManaged contextDocumented mechanism, not a performance score.
Lifecycle & recoveryCheckpoint/rewindDocumented mechanism, not a performance score.
ObservabilitySession onlyDocumented mechanism, not a performance score.
VerificationTool-assistedDocumented mechanism, not a performance score.
Governance & permissionsApproval promptsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

4/5public artifacts present

Security policy: Not found
CI workflow: Present at inspected commit
Automated tests: Present at inspected commit
Evaluation assets: Present at inspected commit
Contributor documentation: Present at inspected commit

The v0.86.2 tree contains 85 test-like files, ten workflows, contributor documentation, and 25 benchmark/evaluation-like assets but no repository security policy. Its model-oriented benchmark is maintained by the product project and is not independent harness evidence, so no product score is imported.

Inspect commit 253f0368b873ba30d8ee26e463718f0c03614ddf, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs

Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage

Latest stable releasev0.86.0Released 2025-08-09; 0 stable releases in 90 daysOpen release
OpenRouter 30d tokens14.84B#52 coding app; 2026-08-09 to 2026-09-07Open app page
Homebrew 30d events608Formula: aiderOpen artifact
GitHub stars48.83KFull-source repository; 4.93K forksOpen artifact