Head to head · Multi-agent orchestration · October 2026 research run
boxes.dev vs Clawboo
Clawboo scores 65.1 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for Developers who want Claude Code or Codex running on cloud copies of their dev environment, started from Slack, Linear, a schedule, an API call or another assistant.
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Clawboo loses 4 points for them
Watch for
No status page, incident history or SLA found
Clawboo B
Best 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
- Reliability, 52 against 32
- Schema & documentation, 83 against 57
- Agent ergonomics, 75 against 60
- Payments & pricing, 90 against 50
Also in its favour
- No key needed to call it
- Free to start without a card
- 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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Clawboo +40
boxes.dev 50
No x402, MPP or L402 (0). Plan prices are public ($19, $99 and $249 a seat a month) and extra usage is $0.40 a box-hour, with a box-hour defined as one hour of a 4 vCPU, 8 GiB devbox (30). A free trial of 20 box-hours. The help page says some teams must add a payment method before starting, so a card-free start is not certain (20 of 30). A person signs in with Google or Apple and approves the OAuth grant or creates the automation secret in the desktop app (0). 0+30+20+0 = 50.
Clawboo 90
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Schema & documentation Clawboo +26
boxes.dev 57
No OpenAPI document, and the MCP tool list could not be read because the endpoint answers 401 before initialize without an OAuth token. The automation API's request and response fields are documented in prose tables (5 of 25). llms.txt with every help page listed (10). The help pages say when to target a new devbox, an existing devbox or an existing thread, when to steer a busy agent and when to wake a devbox first (16). Field tables with enum values such as backend (codex or claude), delivery (steer or next) and four run statuses, and unknown fields are rejected. The MCP schemas themselves were not seen (9 of 15). curl examples and named errors such as 409 devbox_unavailable, 409 thread_unavailable and 503 devbox_wake_failed, with what each means (12). /v1 in the API path on the home page, a single dated product update of 27 October 2026 and no changelog (5 of 15). 5+10+16+9+12+5 = 57.
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).
Reliability Clawboo +20
boxes.dev 32
Hosted reading, for the remote MCP server at api.boxes.dev/mcp and the automation run endpoints. No status page found. The site footer says "All systems normal" with no link, and the trust centre at trust.boxes.dev draws in a script our reader could not run (0). No readable incident history (5). No request rate limits found. Plans cap awake devboxes (3 on the trial, 5 to 25 on paid plans), and the API answers 409 active_fork_limit_reached at the cap (5 of 15). The automation API takes an Idempotency-Key and returns the original run on a retry with idempotentReplay: true, and the MCP connection retries a lost start or message with the same request key. No Retry-After or backoff guidance found (12 of 15). No SLA found (0). Neither the MCP connection nor the automation API is marked beta, and the product launched in June 2026 per its own blog (10). 0+5+5+12+0+10 = 32.
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).
Agent ergonomics Clawboo +15
boxes.dev 60
The MCP tool count is unknown. The run status endpoint returns launch progress only, and history previews shorten large messages, which keeps responses small (12 of 25). Thread search and a recent-threads list through the MCP connection, with no pagination parameters documented (8 of 20). Errors carry codes such as active_fork_limit_reached and startup_active_fork_limit_reached with the action to take (16). Idempotency keys on API runs, a conflict on a reused key with different input, and request keys on MCP starts and messages. Tool annotations could not be read (16 of 20). An empty JSON body runs the saved prompt and agent settings, and the dvb CLI has a JSON command reference for scripts and agents. No SDK (8 of 15). 12+8+16+16+8 = 60.
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).
Score by category
| Category | Weight | boxes.dev | Clawboo | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 52 | Clawboo +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 83 | Clawboo +26 |
| Agent ergonomics | 13% | 60 | 75 | Clawboo +15 |
| Security & auth | 14% | 69 | 70 | Clawboo +1 |
| Payments & pricing | 10% | 50 | 90 | Clawboo +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 51 | Clawboo +3 |
| Transparency & trust | 7% | 60 | 58 | boxes.dev +2 |
| Negative events | ≤15 | 0 | -4 | |
| Total | D 53.2/100 | B 65.1/100 |
Facts side by side
| Fact | boxes.dev | Clawboo |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | Sanreds |
| Hosted endpoint | https://api.boxes.dev/mcp | no (local only) |
| Transports | Streamable HTTP, HTTP | |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSED | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-10-21 |
| Terms last updated | 2026-10-20 | no document linked |
| Privacy policy last updated | 2026-10-21 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 100 npm/wk |
How the scores have moved
boxes.dev
No score change since it was listed.
Verdicts
boxes.dev
An outside agent can start Claude Code or Codex tasks on cloud devboxes through an OAuth MCP server with four scopes, or an automation endpoint with idempotency keys. No status page, SLA or tool schema could be read, and every route starts with a person setting up a project in the app.
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.
Before you call either
boxes.dev
- Send a new
Idempotency-Keyfor each intended run, and the same key and body when you retry an uncertain request - Wait for status
thread_readybefore you use a returneddevboxIdas a target - If you get 409
active_fork_limit_reached, free an awake devbox or wait. The plan's awake-devbox cap is full - Read the thread in boxes.dev for the agent's answer. The status URL does not return it
- Ask for
threads:readonly unless the task needs to start agents or change settings
Clawboo
- Run
npx clawboo@latest, not a barenpx clawboo, which can reuse an older cached build. Node.js 22.12 or newer is required - On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny
/api/mcp/at the proxy and setSTUDIO_ACCESS_TOKENfromopenssl rand -hex 24 - Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
- Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
- Install
@anthropic-ai/claude-agent-sdkglobally beside Clawboo for Claude Code teammates. A one-offnpxrun cannot load it
Questions
Which is better for AI agents, boxes.dev or Clawboo?
Clawboo scores 65.1 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories.
Can an agent call boxes.dev and Clawboo without installing anything?
boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp. No hosted endpoint is listed for Clawboo.
Are boxes.dev and Clawboo open source?
No open-source release is listed for boxes.dev. Clawboo is open source (MIT).
Other comparisons with boxes.dev or Clawboo
- Agent Zero vs boxes.dev
- Aider vs boxes.dev
- Amp vs boxes.dev
- Antigravity CLI vs boxes.dev
- Auggie CLI vs boxes.dev
- AXLR vs boxes.dev
- boxes.dev vs Claude Code
- boxes.dev vs Click
- boxes.dev vs Cline
- boxes.dev vs Conductor
- boxes.dev vs Crush
- boxes.dev vs Cursor CLI
- boxes.dev vs DeepSeek Harness (dsh)
- boxes.dev vs dsh-superagent (DeepSeek)
- boxes.dev vs Devin
- boxes.dev vs Droid CLI
- boxes.dev vs Pi
- boxes.dev vs Emdash
- boxes.dev vs Friday
- boxes.dev vs Gemini CLI
- boxes.dev vs GitHub Copilot CLI
- boxes.dev vs goose
- boxes.dev vs Harness²
- boxes.dev vs HarnessRouter
- boxes.dev vs Jules
- boxes.dev vs Junie CLI
- boxes.dev vs Kilo Code CLI
- boxes.dev vs Kimi Code CLI
- boxes.dev vs Kiro CLI
- boxes.dev vs Letta
- boxes.dev vs mini-swe-agent
- boxes.dev vs MiniMax Code
- boxes.dev vs Mistral Vibe CLI
- boxes.dev vs Muse Code
- boxes.dev vs OpenAI Agents API
- boxes.dev vs OpenAI Codex
- boxes.dev vs OpenCode
- boxes.dev vs OpenHands
- boxes.dev vs OpenMausBot
- boxes.dev vs Orca
- boxes.dev vs Paseo
- boxes.dev vs Prime Agent
- boxes.dev vs Qoder CLI
- boxes.dev vs Qwen Code
- boxes.dev vs Mirror CLI
- boxes.dev vs Rovo Dev CLI
- boxes.dev vs Sculptor
- boxes.dev vs T3 Code
- boxes.dev vs Traycer
- boxes.dev vs Unstoppable
- boxes.dev vs Verdent
- boxes.dev vs Vibe-Trading
- boxes.dev vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs Clawboo
- Amp vs Clawboo
- Antigravity CLI vs Clawboo
- Auggie CLI vs Clawboo
- AXLR vs Clawboo
- boxes.dev vs CLI Manager
- boxes.dev vs Harness
- boxes.dev vs herdr
- boxes.dev vs Paperclip
- boxes.dev vs Parallax
- Claude Code vs Clawboo
- Clawboo vs CLI Manager
- Clawboo vs Cline
- Clawboo vs Conductor
- Clawboo vs Crush
- Clawboo vs DeepSeek Harness (dsh)
- Clawboo vs dsh-superagent (DeepSeek)
- Clawboo vs Devin
- Clawboo vs Droid CLI
- Clawboo vs Emdash
- Clawboo vs Friday
- Clawboo vs Gemini CLI
- Clawboo vs GitHub Copilot CLI
- Clawboo vs goose
- Clawboo vs Harness
- Clawboo vs HarnessRouter
- Clawboo vs herdr
- Clawboo vs Jules
- Clawboo vs Junie CLI
- Clawboo vs Kilo Code CLI
- Clawboo vs Kimi Code CLI
- Clawboo vs Kiro CLI
- Clawboo vs Letta
- Clawboo vs MiniMax Code
- Clawboo vs Mistral Vibe CLI
- Clawboo vs Muse Code
- Clawboo vs OpenCode
- Clawboo vs OpenHands
- Clawboo vs OpenMausBot
- Clawboo vs Orca
- Clawboo vs Paperclip
- Clawboo vs Parallax
- Clawboo vs Paseo
- Clawboo vs Prime Agent
- Clawboo vs Qoder CLI
- Clawboo vs Qwen Code
- Clawboo vs Mirror CLI
- Clawboo vs Rovo Dev CLI
- Clawboo vs Sculptor
- Clawboo vs T3 Code
- Clawboo vs Traycer
- Clawboo vs Unstoppable
- Clawboo vs Verdent
- Clawboo vs Vibe-Trading
- Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-clawboo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/clawboo.json - From a terminal
anchor compare boxes-dev clawboo(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "clawboo"}at/mcp, no key