# Agent Zero vs Paseo (slim)

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

- Full: https://www.anchorterminal.com/compare/agent-zero-vs-paseo.md (~4,500 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/agent-zero-vs-paseo.json · canonical https://www.anchorterminal.com/compare/agent-zero-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 Agent Zero's 46 (D), and leads in 4 of 7 scored categories. Agent Zero leads on reliability. Both do agent harnesses.

- Agent Zero: D 46, rank #1168 of 1486 · https://www.anchorterminal.com/tools/agent-zero.min.md
- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- Agent Zero, good for A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory. Ahead on Reliability, 57 against 50.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Agent ergonomics, 70 against 62. Also No incidents deducted, where Agent Zero loses 15 points for them.

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

| Fact (where they differ) | Agent Zero | Paseo |
| --- | --- | --- |
| Vendor | Agent Zero, s.r.o. | Mohamed Boudra |
| Licence | MIT | Apache-2.0 |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-11-07 |
| Popularity | 19k stars | none |

Why the edge:
- Agent ergonomics, Paseo +8: Agent Zero 62 (Harness reading, scored on what a person or program driving it must supply. Skills load on demand, blocked tools are removed from the prompt, chats can be compacted, and the v2.12 notes report Codex input falling from about 16.4K to 11.3K tokens, a vendor figure (18 of 25). An MCP tool timeout of 120 seconds, a limit of five consecutive unusable responses and context-window handling are set by default. No turn or spend limit was found in the reviewed docs (11 of 20). Other programs reach it through `POST /api_message`, an optional MCP server, A2A and an ACP bridge, with request and response shapes left to the source (11 of 20). An error-retry plugin, saved chats, a message queue, backups and Time Travel snapshots with diff and revert (14 of 20). One Docker command starts it and a wizard sets the model, but there is no SDK and the default has no login (8 of 15).); 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).)
- Reliability, Agent Zero +7: Agent Zero 57 (Read with the local-software lines, as software the owner runs. Installs from the `agent0ai/agent-zero` Docker image, an install script, or a desktop Launcher with builds for macOS, Linux and Windows on x86 and ARM64. The README says it runs wherever Docker runs. The image registry page was not read (17 of 20). The repository holds 245 files under tests/ on 4 November, and its only two workflows still publish Docker images and close inactive issues. The publish workflow runs no tests, so no public CI run shows them passing (5 of 25, a partial kept). 139 open issues and pull requests on 12 October 2026, per that check (GitHub's pages and API weren't read on 4 November). Open reports from September include a crash of `run_ui` after a failed memory consolidation (#1909), a browser worker that hangs the agent turn (#1923) and truncated backups (#1904), each with no reply or one, and a workflow closes anything inactive for 90 days (11 of 25). Release notes for v2.11, v2.12 and v2.13 carry a Breaking Changes section, but breaking changes ship in minor versions, so the numbering is not semver (9 of 15). v2.15, past 1.0 (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.)