# Clawboo vs Paseo (slim)

> Paseo and Clawboo score within a point of each other for multi-agent orchestration, 62.1 and 61.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawboo-vs-paseo.md (~5,250 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-paseo.json · canonical https://www.anchorterminal.com/compare/clawboo-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 and Clawboo score within a point of each other on agent readiness, 62.1 (B) and 61.4 (C). Clawboo leads on schema & documentation, agent ergonomics and security & auth. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #616 of 1510 · https://www.anchorterminal.com/tools/clawboo.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Clawboo, good for One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work. Ahead on Schema & documentation, 83 against 65; Agent ergonomics, 75 against 70; Security & auth, 70 against 58. 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 Maintenance & community, 75 against 51; Transparency & trust, 68 against 58. Also No incidents deducted, where Clawboo loses 4 points for them.

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

| Fact (where they differ) | Clawboo | Paseo |
| --- | --- | --- |
| Vendor | Sanreds | Mohamed Boudra |
| Licence | MIT | Apache-2.0 |
| llms.txt | yes | no |
| Last release | 2026-10-21 | 2026-11-07 |
| Popularity | 100 npm/wk | none |

Why the edge:
- Maintenance & community, Paseo +24: Clawboo 51 (0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).); 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, Clawboo +18: Clawboo 83 (Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Security & auth, Clawboo +12: Clawboo 70 (Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for `clawboo`, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).); Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.)
- Transparency & trust, Paseo +10: Clawboo 58 (MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)
- Agent ergonomics, Clawboo +5: Clawboo 75 (Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).); 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).)