# Pi vs Paseo (slim)

> Pi and Paseo score within a point of each other for agent harnesses, 62.6 and 62.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/earendil-pi-vs-paseo.md (~5,150 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/earendil-pi-vs-paseo.json · canonical https://www.anchorterminal.com/compare/earendil-pi-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)

Pi and Paseo score within a point of each other on agent readiness, 62.6 (B) and 62.1 (B). Both do agent harnesses.

- Pi: B 62.6, rank #550 of 1510 · https://www.anchorterminal.com/tools/earendil-pi.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Pi, good for Developers and pipelines that want a small, scriptable coding agent they can extend in TypeScript and drive over JSONL or RPC, inside their own container. Ahead on Reliability, 75 against 50; Schema & documentation, 84 against 65; Agent ergonomics, 76 against 70; Maintenance & community, 87 against 75. 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. Also No incidents deducted, where Pi loses 10 points for them.

| Category | Pi | Paseo |
| --- | --- | --- |
| Reliability (16%) | 75 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 65 |
| Agent ergonomics (13%) | 76 | 70 |
| Security & auth (14%) | 61 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 87 | 75 |
| Transparency & trust (7%) | 67 | 68 |

| Fact (where they differ) | Pi | Paseo |
| --- | --- | --- |
| Vendor | Earendil | Mohamed Boudra |
| Licence | MIT | Apache-2.0 |
| Last release | 2026-10-21 | 2026-11-07 |
| Popularity | 113k stars, 5.2M npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Reliability, Pi +25: Pi 75 (Read as a local package. `@earendil-works/pi-coding-agent` 1.4.0 on npm (still the latest on 1 November 2026) with Node.js 22.19 or newer stated, install scripts for macOS, Linux and Windows, Nix and standalone binaries (20). A public CI workflow builds, checks and tests on every push to main and runs an MCP client conformance job. The run on the commit we cloned (ce950d7, 8 October 2026) passed, but eight of the last 15 runs on main, all on 7 and 8 October, failed. Run results weren't readable on 23 October, so this stands per the 8 October check (15). The repository API reported 308 open issues and pull requests against 113,417 stars on 8 October, not re-read on 23 October. Issues from new contributors are closed automatically and reviewed daily by maintainers, per CONTRIBUTING.md, so the open count understates what is reported, and we couldn't sample reply times (16). A dated changelog with Breaking Changes sections and migration steps, but breaking changes ship outside major versions. The Azure provider rename shipped in patch release 1.0.3 on 5 October 2026, minor release 1.2.0 on 12 October carried four (theme schema location, `before_agent_start`, busy-session behaviour and `pi mcp list --json` output), and 1.3.0 required `/v1` on `kimi-coding` base URL overrides under Changed. The same reading as agent-zero and mistral-vibe-cli, and these breaks also take a deduction under negative events (9). 1.4.0 on 21 October 2026, with 1.0.0 dated 1 October 2026 (15).); 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.)
- Schema & documentation, Pi +19: Pi 84 (Harness reading, as for the other harnesses. JSON Schemas for settings, models, keybindings and themes ship in the package and, since 1.2.0 on 12 October 2026, at pi.dev/schemas/, and the JSON event stream and every RPC command are documented record by record, but as Markdown and TypeScript types with no machine-readable spec for the RPC protocol (18). pi.dev/llms.txt returns 404. Each docs page answers `Accept: text/markdown` with Markdown, and the docs ship inside the npm package (8). The integration page has a table saying when to use interactive, print, JSON, RPC or the SDK, and the MCP page gives a typical use for each exposure setting. 1.4.0 adds a Models Configuration reference generated from the `models.json` schema (17). Enumerated modes, thinking levels and exposure values, typed settings with defaults (13). A Python RPC client, a typed TypeScript client and about 75 example extensions, with command errors and parse errors shown as records (13). A dated changelog in the repository and at pi.dev/changelog with an RSS feed (15).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Maintenance & community, Pi +12: Pi 87 (v1.4.0 on 21 October 2026, still the latest on npm on 1 November (30). The changelog dates 23 releases in the 90 days from 3 August, 0.84.0 on 6 August to 1.4.0 on 21 October 2026 (20). Commits land daily and the changelog credits issues and outside pull requests in most releases. New contributors' issues are closed automatically, reviewed daily, and get no reply if they miss the quality bar, per CONTRIBUTING.md. Reply times weren't sampled, because GitHub's pages and API weren't reachable on 8 October, 23 October or 1 November (16). npm, the pi.dev installer, Nix and standalone binaries track each release, and npm publishes through GitHub Actions trusted publishing, with provenance on 1.4.0 (14). Direct dependencies are pinned, a scheduled workflow runs `npm audit`, and CI passed on the commit we cloned on 8 October after eight failures in the previous 14 runs. CI results weren't readable on 23 October or 1 November (7).); 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.)
- Agent ergonomics, Pi +6: Pi 76 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. Four default tools (read, bash, edit, write) and a short system prompt. MCP tools default to `codemode` exposure, which keeps them out of the model's tool declarations, and `tool_search` loads deferred ones on demand (23). Automatic compaction, agent-level retry with three attempts and exponential backoff, and truncated tool output saved to a file. We found no turn or step limit in the CLI or settings reference (13). `--mode json` streams JSONL events ending in `agent_settled` and `--mode rpc` returns `success: false` with an error string. Print mode exits nonzero on a failed response, JSON mode doesn't (16). Sessions are stored as trees and continue, fork or take a fixed ID with `--continue`, `--fork` and `--session-id`. File changes have no built-in undo, and a git checkpoint is an example extension (14). It needs a provider key or subscription login before the first run, and the SDK is TypeScript only, with RPC for other languages (10).); 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).)