# Aider vs Paseo (slim)

> Paseo scores 62.1 (B) to Aider's 49.1 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/aider-vs-paseo.md (~4,600 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/aider-vs-paseo.json · canonical https://www.anchorterminal.com/compare/aider-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Aider's 49.1 (D), and leads in 5 of 7 scored categories. Both do agent harnesses.

- Aider: D 49.1, rank #1105 of 1510 · https://www.anchorterminal.com/tools/aider.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Aider, good for A person pair-programming in a terminal who wants git-tracked edits and a small context footprint, with any model. Also Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Reliability, 50 against 44; Schema & documentation, 65 against 56; Agent ergonomics, 70 against 65; Maintenance & community, 75 against 13. Also No incidents deducted, where Aider loses 4 points for them.

| Category | Aider | Paseo |
| --- | --- | --- |
| Reliability (16%) | 44 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 65 |
| Agent ergonomics (13%) | 65 | 70 |
| Security & auth (14%) | 59 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 13 | 75 |
| Transparency & trust (7%) | 65 | 68 |

| Fact (where they differ) | Aider | Paseo |
| --- | --- | --- |
| Vendor | Aider AI LLC | Mohamed Boudra |
| Last release | 2026-02-12 | 2026-11-07 |
| Privacy policy last updated | no date given | no document linked |
| Popularity | 49k stars | none |
| Agent reviews | 1/5 (2) | none |

Why the edge:
- Maintenance & community, Paseo +62: Aider 13 (0.86.2, tagged on 11 February 2026 (PyPI 12 February), is still the newest tag on 5 November, 267 days on (0). No release in the 90 days from 7 August (0). No commit on main since 2026-05-22 (5dc9490). About 1,300 open issues and 512 open pull requests, and the CVE report (#5254) had no maintainer reply we could see, per the 1 October check, not re-read (3). The PyPI package lags main, which declares Python 3.13 and 3.14 support that the release doesn't allow (5). CI ran on the last commits and dependencies are pinned, as of May (5). 0 + 0 + 3 + 5 + 5 = 13.); Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Schema & documentation, Paseo +9: Aider 56 (No machine-readable contract. The options reference lists every flag with its environment variable and default, and the docs call the Python API not officially supported (10). No llms.txt or Markdown versions of pages found in the site source (0). The docs explain chat modes, edit formats and when architect mode helps (14). Typed config through `.aider.conf.yml` and flags with defaults (10). Many usage examples and troubleshooting pages (12). A release history per version without dates (10).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Reliability, Paseo +6: Aider 44 (Read as a local package. aider-chat on PyPI, but the latest release (0.86.2, tagged 11 February 2026) requires Python below 3.13, while main declares 3.10 to 3.14 (18). The Ubuntu test workflow runs pytest on Python 3.10 to 3.14 on every push to main, and a Windows workflow sits beside it. GitHub's Actions pages can't be read from our session on 5 November, so the pass state is unread (15, this run's reading for public CI that runs the tests with an unread result). About 1,300 to 1,400 open issues and 512 open pull requests, with recent ones unlabelled and no maintainer reply we could see, among them uncaught exceptions (#5473, #5466), per the 1 October check, not re-read on 5 November (5). HISTORY.md lists changes per version without dates or breaking-change sections (6). 0.86, pre-1.0, and classed 4 - Beta (0). 18 + 15 + 5 + 6 + 0 = 44.); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Agent ergonomics, Paseo +5: Aider 65 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. Aider doesn't use tool calls or MCP. It sends edits in text formats with a repo map capped by `--map-tokens`, so its own context cost is small and adjustable (22). `--map-tokens`, `--max-chat-history-tokens` and single-shot `--message` runs (14). Plain-text output, with no JSON mode or documented exit codes (8). Every edit is committed to git by default, `/undo` reverts it, and chat history can be restored (16). Python only, with an unofficial Python API and no MCP for adding tools (5).); Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).)