# Clawboo vs Prime Agent (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.md (~6,100 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-prime-agent
- 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-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Clawboo and Prime Agent score within a point of each other on agent readiness, 61.4 (C) and 60.7 (C). Prime Agent leads on reliability, maintenance & community and transparency & trust. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Prime Agent: C 60.7, rank #589 of 1251 · https://www.anchorterminal.com/tools/prime-agent.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 42; Security & auth, 70 against 50.
- Prime Agent, good for Long-running research and coding work where one model drives subagents, schedules and goals from code, and where the owner can isolate the machine. Ahead on Reliability, 65 against 52; Maintenance & community, 79 against 51; Transparency & trust, 67 against 58. Also No incidents deducted, where Clawboo loses 4 points for them.

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

| Fact (where they differ) | Clawboo | Prime Agent |
| --- | --- | --- |
| Vendor | Sanreds | Prime Intellect |
| llms.txt | yes | no |
| Last release | 2026-10-21 | 2026-10-07 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 100 npm/wk | 22k stars |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Schema & documentation, Clawboo +41: 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).); Prime Agent 42 (Harness reading of the framework line. `--mode json` emits a session event stream and `rpc` and `acp` modes exist, but we found no published schema or reference for them outside the source (10). docs.primeintellect.ai serves an llms.txt that has no Prime Agent page (0). The README states what the agent does, how it differs and that it is not a sandbox, and the bundled skills say when to use each function (10). CLI values are validated with messages that list the valid choices, and MCP tool schemas are read live from the server (7). The README gives the install line and seven commands, and the MCP skill documents its error types, but there is no headless or configuration guide (5). Versioned releases with notes for stable versions, none of substance for nightlies (10).)
- Maintenance & community, Prime Agent +28: 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).); Prime Agent 79 (Nightly v0.9.9-beta.55 on 7 October 2026 and stable v0.9.8 on 29 September 2026 (30). At least 12 stable tags since 20 August 2026 and 55 nightly betas since 30 September (20). The main branch had at least 200 commits between 22 September and 8 October, and Discussions had new threads daily in October, but issues from unapproved contributors and unsolicited pull requests are closed automatically and we could not read reply times (14). Binaries for five targets from one release workflow and Homebrew definitions in the repository. No SDK and no registry package found (8). A pinned toolchain, a committed lockfile, cargo-deny with two triaged advisory exceptions reviewed on 17 September 2026, and CI passing. An open issue (#3292) reports npm audit findings for the 0.9.8 install, which we did not verify (7).)
- Security & auth, Clawboo +20: 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).); Prime Agent 50 (Harness reading of the framework checklist, as used 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. Usage telemetry is on by default. It is pseudonymous, limited to primitive values with no prompts, tool content or file paths per the source, disclosed on first run and mirrored to a local `telemetry.jsonl` (18). No approval prompts were found and there is no sandbox, which the README states. MCP tools can be limited with `enabledTools` and `disabledTools`, and the agent is told to recommend a connection, not make one (4). The README tells users to work only with trusted repositories, instructions and skills. No detection or mitigation found (5). Append-only JSONL session files, a `prime-agent incident` timeline command and the local telemetry mirror (12). The vendor's security policy has a reporting address, safe harbour, response times and discretionary rewards, scoped to its website and API. The repository has no SECURITY.md and no published advisories, CONTRIBUTING.md says to report privately without naming an address, and security.txt returned 404. cargo-deny runs in CI (11).)
- Reliability, Prime Agent +13: Clawboo 52 (Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).); Prime Agent 65 (Read with the local-software lines. The vendor's installer fetches checksummed binaries for macOS and Linux on x64 and arm64, with an npm install needing Node.js 20.6 or later as the fallback, but the stable pointer is the TypeScript build while the Rust code on main ships only on the nightly channel, and Windows builds are beta only (17). A public CI workflow runs fmt, clippy with warnings as errors, sharded workspace tests and cargo-deny, and its badge read passing on 8 October 2026 (25). 20 open issues and 91 open pull requests on 8 October. Issues hold only work the maintainers accepted, and the Discussions bug category lists reports from the past two weeks of session-worker crashes, truncated RPC output and provider hangs, whose reply state we did not read (15). Stable releases carry written notes and changes are recorded as fragments in `.changes`, including the removal of the `--tools` flags, but there is no changelog file, the nightly notes are boilerplate and the project is at 0.x (8). Version 0.9.8, and the Rust build is a beta (0).)
- Transparency & trust, Prime Agent +9: 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).); Prime Agent 67 (MIT in the LICENSE file and Cargo.toml, with a notice that the code is a port of a TypeScript product originally copyright Mario Zechner (30). The first-run notice and the telemetry crate README say what is sent and what is excluded, and name the endpoint and PostHog, but the vendor privacy policy is dated 23 February 2024, does not describe agent telemetry and gives no retention period for it (12). No deprecation policy found. Removed flags are recorded in change fragments (5). Telemetry is disclosed with a setting, a command and two environment variables to turn it off (20).)