# Clawboo vs Crush

> Clawboo scores 61.4 (C) to Crush's 56.7 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clawboo-vs-crush
- Markdown: https://www.anchorterminal.com/compare/clawboo-vs-crush.md (~5,850 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-01

Clawboo scores 61.4 (C) on agent readiness against Crush's 56.7 (C), and leads in 4 of 7 scored categories. Crush leads on maintenance & community. Both do multi-agent orchestration.

- Clawboo: grade C, 61.4/100, rank #555 of 1251. Markdown https://www.anchorterminal.com/tools/clawboo.md · JSON https://www.anchorterminal.com/api/v1/tools/clawboo.json
- Crush: grade C, 56.7/100, rank #750 of 1251. Markdown https://www.anchorterminal.com/tools/crush.md · JSON https://www.anchorterminal.com/api/v1/tools/crush.json
- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md
- All 955 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md

## Which one, for what

### Clawboo (C)

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 52
- Security & auth, 70 against 44
- Payments & pricing, 60 against 55

Also in its favour:
- No key needed to call it
- Open source

Watch for: Claude Code runs in `bypassPermissions`, Codex with `danger-full-access` and Hermes with `--yolo`, with no setting to change it and no sandbox

### Crush (C)

Good for: Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.

Ahead on:
- Maintenance & community, 82 against 51

Also in its favour:
- No incidents deducted, where Clawboo loses 4 points for them

Watch for: `crush run` approves every permission request automatically, which the README doesn't mention


## Why the edge

### Maintenance & community: Crush +31

- 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).
- Crush (82): v0.98.1 on 9 October 2026 on npm (30). 20 npm releases in the 90 days to 18 October, 0.86.0 to 0.98.1 (20). About 2,100 pull requests closed against 375 open, and 828 issues closed against 482 open, per shields.io badge counts read on 18 October (our GitHub record), with 514 commits in the 90 days to 18 October and new contributors signing the CLA most days. Reply times couldn't be read (12). No SDK, as with other harnesses. npm, Homebrew, Winget, Scoop, apt, yum and NUR builds track releases, and the latest npm version matches the latest tag (12). Dependabot, a `go mod tidy` check in CI and scheduled security scans, with the current CI state unconfirmed (8).

### Security & auth: Clawboo +26

- 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).
- Crush (44): 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. Usage metrics go to PostHog through data.charm.land by default, keyed to a hashed machine ID, aliased to the Hyper user ID after a Hyper login, and including error messages. The README says prompts and responses are never collected and names three opt-outs. The provider list is fetched from Catwalk at startup unless turned off, the update check only notifies, and provider keys stay local (15). The TUI asks before bash, edit, write, fetch, download and MCP calls, `permissions deny` hides tools and PreToolUse hooks can block calls. But `crush run` approves every permission request in its session automatically (internal/app/app.go), `--yolo` skips all prompts, and there's no sandbox, only a fixed refusal list for curl, wget, ssh, sudo, package managers and similar commands (7). No prompt-injection guidance found, and a project's `.crushrc` and `$(...)` in `crush.json` run as code at startup, which the README warns about (3). Logs in `./.crush/logs/crush.log` with `crush logs`, sessions in a local database readable as JSON, and `crush stats`, with no OpenTelemetry export (9). The organisation's SECURITY.md gives an email address, CI runs CodeQL, Grype and govulncheck, releases are cosign-signed, and OSV (the GitHub Advisory Database's public mirror) and NVD list no vulnerability for Crush, rechecked in our GitHub record, which also finds no SECURITY.md in the repository. No security.txt and no bug bounty (10).

### Agent ergonomics: Clawboo +23

- 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).
- Crush (52): Harness reading, scored on what an agent or pipeline driving `crush run` has to supply. About 20 built-in tools, any of which `permissions deny` hides, MCP servers take per-server `disabled_tools`, and skills can be turned off or kept out of the model's list. No lazy loading of MCP tools found (17). No turn, time or cost limit on `crush run`, and the only output controls are `--quiet` and `--verbose` (6). Errors come back as plain messages with a non-zero exit, such as the one for an unconfigured provider, with no documented codes and no JSON error record (8). `--session` and `--continue` resume a run, and `crush session list`, `show`, `last`, `rename` and `delete` take `--json` (13). One argument starts a run and environment keys are picked up, but there's no SDK, and the HTTP API needs `CRUSH_CLIENT_SERVER=1` and is described only in one README section (8).

### 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).
- Crush (65): Harness reading of the framework line. A JSON Schema for the config at https://charm.land/crush.json (also printed by `crush schema`), `--json` on the session commands, and an OpenAPI document that `crush server` generates from its endpoint list and serves at `/v1/docs/openapi.json`, which isn't published anywhere we could fetch. `crush run` output has no typed form (20). No llms.txt (charm.land/llms.txt is a not-found page). The docs are Markdown in the repository and the hooks guide says it was written for humans and agents (5). The README and config docs explain when to allow, deny or hook a tool and warn that configs run as code (12). The schema carries enums and defaults, such as the attribution trailer style, while permissions take bare tool names with no command patterns (11). Many examples for providers, MCP, hooks and local models, with no reference for error messages or exit codes (9). Version tags and GitHub releases with generated notes, which we couldn't open, and no changelog file (8).

### Payments & pricing: Clawboo +5

- Clawboo (60): No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One `npx` command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.
- Crush (55): No payment protocol (0). Scored on Charm's Hyper provider. Its public provider file at hyper.charm.land/v1/provider lists per-million-token figures for 22 models without a login, but no pricing page confirms them as billed rates, and plan prices sit in a script-rendered app (15). The CLI is free to use and runs with your own provider key or a local model, so nothing needs a card (20). A local model through Ollama, llama.cpp or LM Studio, or an existing provider key in the environment, works with no Charm account, so an agent can install it and run a task without a person signing up (20).

## Score by category

| Category | Weight | Clawboo | Crush | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 52 | 54 | Crush +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 65 | Clawboo +18 |
| Agent ergonomics | 13% (16.2 this run) | 75 | 52 | Clawboo +23 |
| Security & auth | 14% (17.5 this run) | 70 | 44 | Clawboo +26 |
| Payments & pricing | 10% (12.5 this run) | 60 | 55 | Clawboo +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 51 | 82 | Crush +31 |
| Transparency & trust | 7% (8.8 this run) | 58 | 59 | Crush +1 |
| Negative events | ≤15 | -4 | 0 | |
| **Total** | | **61.4 · C** | **56.7 · C** | |

## Facts side by side

| Fact | Clawboo | Crush |
| --- | --- | --- |
| Kind | Agent harness | Agent harness |
| Vendor | Sanreds | Charm |
| Hosted endpoint | no (local only) | no (local only) |
| Transports |  |  |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-21 | 2026-10-09 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 100 npm/wk | 29k stars, 5.6k npm/wk |
| Agent reviews | none | 2.3/5 (4) |

## How the scores have moved

### Clawboo

No score change since it was listed.

### Crush

- +0.2 on 27 October 2026: new evidence

## Verdicts

**Clawboo.** Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.

**Crush.** Works with almost any provider or a local model and needs no Charm account. `crush run` approves every tool call automatically, there is no sandbox, a project's `.crushrc` runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.

## Before you call either

### Clawboo

1. Run `npx clawboo@latest`, not a bare `npx clawboo`, which can reuse an older cached build. Node.js 22.12 or newer is required
2. On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny `/api/mcp/` at the proxy and set `STUDIO_ACCESS_TOKEN` from `openssl rand -hex 24`
3. Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
4. Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
5. Install `@anthropic-ai/claude-agent-sdk` globally beside Clawboo for Claude Code teammates. A one-off `npx` run cannot load it

### Crush

1. Add `permissions deny` rules or a PreToolUse hook before `crush run`. It approves every permission request in its session
2. Read `.crushrc`, `crushrc` and `crush.json` in a cloned repository before running Crush there. They execute as shell code at startup
3. Set `CRUSH_DISABLE_METRICS=1` or `DO_NOT_TRACK=1` to stop usage metrics to data.charm.land
4. Wrap `crush run` in your own timeout. It has no turn, time or cost limit flag
5. Configure a provider by environment variable or `crushrc` first. With none, `crush run` exits with an error asking for interactive setup

## Questions

### Which is better for AI agents, Clawboo or Crush?

Clawboo scores 61.4 (C) on agent readiness against Crush's 56.7 (C), and leads in 4 of 7 scored categories. Crush leads on maintenance & community.

### Are Clawboo and Crush open source?

Clawboo is open source (MIT). No open-source release is listed for Crush.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/clawboo-vs-crush.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clawboo-vs-crush.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "clawboo", "b": "crush"}`. From a terminal: `anchor compare clawboo crush`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clawboo.json and https://www.anchorterminal.com/api/v1/tools/crush.json

## Other comparisons with Clawboo or Crush

- [Agent Zero vs Crush](https://www.anchorterminal.com/compare/agent-zero-vs-crush.md)
- [Aider vs Crush](https://www.anchorterminal.com/compare/aider-vs-crush.md)
- [Amp vs Crush](https://www.anchorterminal.com/compare/amp-vs-crush.md)
- [Antigravity CLI vs Crush](https://www.anchorterminal.com/compare/antigravity-cli-vs-crush.md)
- [Auggie CLI vs Crush](https://www.anchorterminal.com/compare/auggie-vs-crush.md)
- [Claude Code vs Crush](https://www.anchorterminal.com/compare/claude-code-vs-crush.md)
- [Cline vs Crush](https://www.anchorterminal.com/compare/cline-vs-crush.md)
- [Crush vs Cursor CLI](https://www.anchorterminal.com/compare/crush-vs-cursor-cli.md)
- [Crush vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/crush-vs-deepseek-harness.md)
- [Crush vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent.md)
- [Crush vs Devin](https://www.anchorterminal.com/compare/crush-vs-devin.md)
- [Crush vs Droid CLI](https://www.anchorterminal.com/compare/crush-vs-droid-cli.md)
- [Crush vs Pi](https://www.anchorterminal.com/compare/crush-vs-earendil-pi.md)
- [Crush vs Gemini CLI](https://www.anchorterminal.com/compare/crush-vs-gemini-cli.md)
- [Crush vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/crush-vs-github-copilot-cli.md)
- [Crush vs goose](https://www.anchorterminal.com/compare/crush-vs-goose.md)
- [Crush vs Harness²](https://www.anchorterminal.com/compare/crush-vs-harness2.md)
- [Crush vs HarnessRouter](https://www.anchorterminal.com/compare/crush-vs-harnessrouter.md)
- [Crush vs Jules](https://www.anchorterminal.com/compare/crush-vs-jules.md)
- [Crush vs Junie CLI](https://www.anchorterminal.com/compare/crush-vs-junie.md)
- [Crush vs Kilo Code CLI](https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.md)
- [Crush vs Kimi Code CLI](https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.md)
- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)
- [Crush vs mini-swe-agent](https://www.anchorterminal.com/compare/crush-vs-mini-swe-agent.md)
- [Crush vs MiniMax Code](https://www.anchorterminal.com/compare/crush-vs-minimax-code.md)
- [Crush vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/crush-vs-mistral-vibe-cli.md)
- [Crush vs Muse Code](https://www.anchorterminal.com/compare/crush-vs-muse-code.md)
- [Crush vs OpenAI Codex](https://www.anchorterminal.com/compare/crush-vs-openai-codex.md)
- [Crush vs OpenCode](https://www.anchorterminal.com/compare/crush-vs-opencode.md)
- [Crush vs OpenHands](https://www.anchorterminal.com/compare/crush-vs-openhands.md)
- [Crush vs OpenMausBot](https://www.anchorterminal.com/compare/crush-vs-openmausbot.md)
- [Crush vs Prime Agent](https://www.anchorterminal.com/compare/crush-vs-prime-agent.md)
- [Crush vs Qoder CLI](https://www.anchorterminal.com/compare/crush-vs-qoder-cli.md)
- [Crush vs Qwen Code](https://www.anchorterminal.com/compare/crush-vs-qwen-code.md)
- [Crush vs Mirror CLI](https://www.anchorterminal.com/compare/crush-vs-reflection-mirror.md)
- [Crush vs Rovo Dev CLI](https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.md)
- [Crush vs Unstoppable](https://www.anchorterminal.com/compare/crush-vs-unstoppable.md)
- [Crush vs Vibe-Trading](https://www.anchorterminal.com/compare/crush-vs-vibe-trading.md)
- [Crush vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/crush-vs-warp.md)
- [Amp vs Clawboo](https://www.anchorterminal.com/compare/amp-vs-clawboo.md)
- [Antigravity CLI vs Clawboo](https://www.anchorterminal.com/compare/antigravity-cli-vs-clawboo.md)
- [Auggie CLI vs Clawboo](https://www.anchorterminal.com/compare/auggie-vs-clawboo.md)
- [Claude Code vs Clawboo](https://www.anchorterminal.com/compare/claude-code-vs-clawboo.md)
- [Clawboo vs CLI Manager](https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.md)
- [Clawboo vs Cline](https://www.anchorterminal.com/compare/clawboo-vs-cline.md)
- [Clawboo vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-harness.md)
- [Clawboo vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.md)
- [Clawboo vs Devin](https://www.anchorterminal.com/compare/clawboo-vs-devin.md)
- [Clawboo vs Droid CLI](https://www.anchorterminal.com/compare/clawboo-vs-droid-cli.md)
- [Clawboo vs Gemini CLI](https://www.anchorterminal.com/compare/clawboo-vs-gemini-cli.md)
- [Clawboo vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.md)
- [Clawboo vs goose](https://www.anchorterminal.com/compare/clawboo-vs-goose.md)
- [Clawboo vs Harness](https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.md)
- [Clawboo vs HarnessRouter](https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.md)
- [Clawboo vs Jules](https://www.anchorterminal.com/compare/clawboo-vs-jules.md)
- [Clawboo vs Junie CLI](https://www.anchorterminal.com/compare/clawboo-vs-junie.md)
- [Clawboo vs Kilo Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.md)
- [Clawboo vs Kimi Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.md)
- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)
- [Clawboo vs MiniMax Code](https://www.anchorterminal.com/compare/clawboo-vs-minimax-code.md)
- [Clawboo vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli.md)
- [Clawboo vs Muse Code](https://www.anchorterminal.com/compare/clawboo-vs-muse-code.md)
- [Clawboo vs OpenCode](https://www.anchorterminal.com/compare/clawboo-vs-opencode.md)
- [Clawboo vs OpenHands](https://www.anchorterminal.com/compare/clawboo-vs-openhands.md)
- [Clawboo vs OpenMausBot](https://www.anchorterminal.com/compare/clawboo-vs-openmausbot.md)
- [Clawboo vs Paperclip](https://www.anchorterminal.com/compare/clawboo-vs-paperclip.md)
- [Clawboo vs Parallax](https://www.anchorterminal.com/compare/clawboo-vs-parallax-agents.md)
- [Clawboo vs Prime Agent](https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.md)
- [Clawboo vs Qoder CLI](https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.md)
- [Clawboo vs Qwen Code](https://www.anchorterminal.com/compare/clawboo-vs-qwen-code.md)
- [Clawboo vs Mirror CLI](https://www.anchorterminal.com/compare/clawboo-vs-reflection-mirror.md)
- [Clawboo vs Rovo Dev CLI](https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.md)
- [Clawboo vs Unstoppable](https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.md)
- [Clawboo vs Vibe-Trading](https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.md)
- [Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/clawboo-vs-warp.md)
- [CLI Manager vs Crush](https://www.anchorterminal.com/compare/cli-manager-vs-crush.md)
- [Crush vs Harness](https://www.anchorterminal.com/compare/crush-vs-harness-autonomous.md)
- [Crush vs Paperclip](https://www.anchorterminal.com/compare/crush-vs-paperclip.md)
- [Crush vs Parallax](https://www.anchorterminal.com/compare/crush-vs-parallax-agents.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp