Head to head · Agent harnesses · October 2026 research run
boxes.dev vs HarnessRouter
boxes.dev scores 53.2 (D) on agent readiness against HarnessRouter's 49.3 (D), and leads in 2 of 7 scored categories. HarnessRouter leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust. Both do agent harnesses.
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.
Ahead on
- Security & auth, 69 against 60
- Payments & pricing, 50 against 38
Also in its favour
- No incidents deducted, where HarnessRouter loses 11 points for them
Watch for
No status page, incident history or SLA found
Best for A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.
Ahead on
- Schema & documentation, 83 against 57
- Agent ergonomics, 73 against 60
- Maintenance & community, 72 against 48
- Transparency & trust, 73 against 60
Also in its favour
- Open source
Watch for
No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form
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.
Schema & documentation HarnessRouter +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.
HarnessRouter 83
API reading. UHP's OpenAPI 3.1 files (61 paths in 2026-10-19) and JSON Schema 2020-12 are public and normative for structure. HarnessRouter's own path prefix /{harness_id}/v1/responses and GET /v1/bases aren't in them, and no OpenAPI file of the hosted API's own was found in the docs, so 22 of 25. llms.txt, llms-full.txt, agents.md, docs.md, pricing.md and harnesses.md (10). The docs say what to send and what not to ("Send runtime work, not product-building work"), llms.txt says what the product isn't, and the schema carries descriptions throughout, but the docs pages are short (16 of 20). Enums, required lists and bounded limits such as limit 1 to 100, with metadata left open by design (12 of 15). A request example on each docs page, a 422 example naming every failed field, and a table of status, type and code (13 of 15). Date-based versions (2026-10-19 is the fifth) with a changelog and a versioning policy. Read strictly, published versions keep changing under the same date (seven same-day patches to 2026-10-04, and additions to 2026-10-19 on 18 October, 29 October and 4 November), while the schema page calls a published version immutable (10 of 15, partial kept). The conformance page and the suite's README now agree on 101 checks. 22 + 10 + 16 + 12 + 13 + 10 = 83.
Maintenance & community HarnessRouter +24
boxes.dev 48
Closed service. CLI @boxes-dev/cli 1.0.1134 published on 17 November 2026 (30). Only one dated product update was found, on 27 October 2026, and earlier CLI versions' dates were not read, so three releases in 90 days are not established (0). A support address, an in-app chat and a blog, with no public tracker or changelog (8 of 25). A CLI but no SDK, and no entry in the official MCP registry was looked for (5 of 15). The CLI is published from GitHub Actions with npm trusted publishing and signatures (5 of 10). 30+0+8+5+5 = 48.
HarnessRouter 72
Open-source reading of the repository behind the hosted service. Last tag v0.38.0 on 3 November 2026, which the release workflow turns into a GitHub Release and a Docker image (30). 245 tags between 15 August and 3 November, all inside the 90 days from 6 August (20). GitHub's issue pages and API refused this session, so open issues and reply times are unchecked. Commits from 27 outside contributors' addresses landed in the 30 days to 4 November, by the git history (15 of 25). No official SDK and no MCP server to register (0). A tests workflow runs every suite on each pull request and push to main, with a release workflow and a Docker image, but whether the default branch passes is unchecked (7 of 10). 30 + 20 + 15 + 0 + 7 = 72.
Agent ergonomics HarnessRouter +13
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.
HarnessRouter 73
API reading. Sessions, turns and files are separate reads, and list endpoints take limit and cursor, but there's no field selection on a response (15 of 25). Cursor paging on session and memory lists with a bounded limit, and few filters found (14 of 20). One error envelope with type, code, param and detail, a closed code set, a retry rule per code and a 422 that lists every failed field without echoing the body (18 of 20). Idempotency-Key on task creation, reuse only for the same request, recover from the session after a drop, and an explicit cancel because closing the stream doesn't stop work (18 of 20). Only input is required to run a task, and budgets default to 400 steps, 7,200 seconds and $10. No official SDK, only the OpenAI Responses shape, clients generated from the OpenAPI file and an Agent Skill (8 of 15). 73 in all.
Transparency & trust HarnessRouter +13
boxes.dev 60
Closed service under the Common Paper Cloud Service Agreement 2.1, dated 20 October 2026, with the standard terms' machine-learning clause deleted and California law (15). The privacy policy of 21 October 2026 gives retention by data type (session replay about 30 days, Slack data deleted within 14 business days of disconnecting), and the backup clause matches the terms (22 of 30). Price changes take 30 days' notice under the terms. No deprecation policy for the API or MCP server found (5 of 20). Service providers are named (Convex, Cloudflare Workers, Expo, OpenAI, Amplitude, Sentry, Google and Apple), but the host that runs devboxes is unnamed and data may be processed in the US and elsewhere (12 of 20). 15+22+5+12 = 54.
HarnessRouter 73
Editorial half. The server, specification, schema and conformance suite are Apache-2.0. The Cloud's own billing and deployment wasn't confirmed to match the open code, and the Agent Skill has a custom licence for some guides (25 of 30). The privacy policy, DPA, subprocessor list and a retention page agree. Customer content isn't used for training without an opt-in, and periods are stated (tasks deleted at once, agents and files after 30 days, backups within 14 days, credentials within 90, free-plan task records 7 days). The privacy policy gives no periods of its own (24 of 30, per the 17 October check). Deprecation 15 of 20 (was 14). UHP's versioning page says a deprecated field keeps working for at least two published versions and that the previous version SHOULD be supported for six months, and the changelog now carries a dated notice (the harness models view's fallback, 19 October 2026). The rule is counted in versions, not time, so dated notices give 15. Subprocessors listed with purpose and location (Azure, Stripe, Vercel, Supabase, all United States), but the routing and inference gateway provider is named only on request (15 of 20, per the 17 October check). 25 + 24 + 15 + 15 = 79. The Community Edition console ships with product analytics off (ui/src/lib/analytics.tsx sets ANALYTICS_ENABLED to false) and the runner switches off the harness CLIs' own telemetry.
Payments & pricing boxes.dev +12
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.
HarnessRouter 38
Published rubric, for the hosted service. No machine payment protocol (0). Per-unit prices without a login, agent work per active minute and model calls at listed provider prices per million tokens (20). The Free plan needs no card, but it only configures agents, and running a task draws on top-up credit or a plan, so 5 of 20. A person signs up in a browser and creates the key in the console (0). 0 + 20 + 5 + 0 = 25. Read with the self-hosted rule, the Community Edition with the owner's provider keys would score 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Security & auth boxes.dev +9
boxes.dev 69
OAuth for the MCP server, with protected-resource metadata naming mcp.boxes.dev and four scopes (threads:read, threads:write, events:subscribe, settings:write), a per-project grant and removal from settings. Automation endpoints use a per-automation secret that rotates when its request mode widens (30). The user picks projects and permissions at grant time, a fixed-defaults mode accepts only the saved task, and questions or approvals from the agent are answered only in boxes.dev, never through the MCP connection (15). Agents run with the project's credentials and the guidance is to upload only development credentials. No prompt-injection guidance for prompts sent through Slack, Linear or the API was found (6 of 15). Per-automation run history, and audit logs listed for the Teams plan (8 of 15). A valid security.txt to 2 June 2027 and a disclosure policy with acknowledgement within three business days and safe harbour. No bug bounty and no certification found (10 of 20). 30+15+6+8+10 = 69.
HarnessRouter 60
Hosted reading. Bearer Workspace API keys, revocable at once through the API, held to one workspace or reaching the organisation, with harness-bound calibration credentials. No OAuth, per-endpoint scopes or expiry found (20 of 30). Least privilege 10 of 20. disabled_tools per configured agent, enforced by the runtime only where GET /v1/bases says hard, and per-turn cost and step caps, with no approval step for actions a harness takes. Prompt injection 10 of 15. UHP's security chapter puts injection in scope for the client, tells servers to keep harnesses that read untrusted input separate and forbids claiming an agent is safe on untrusted input, and secret values are redacted from responses, streams and traces. Operator visibility 10 of 15. A cost breakdown per task on every plan, and the step-by-step trace is beta, included in Scale or $50 a month. Security programme 10 of 20 (was 8). A disclosure policy (v1.0, effective 30 July 2026) with safe harbour and no bounty, SECURITY.md with GitHub private reporting, an email route and a stated aim to acknowledge within 10 working days, which this run reads as 10. GHSA identifiers are cited in public fix commits; no security.txt and no SOC 2 or ISO 27001 found. 20 + 10 + 10 + 10 + 10 = 60.
Score by category
| Category | Weight | boxes.dev | HarnessRouter | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 35 | HarnessRouter +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 83 | HarnessRouter +26 |
| Agent ergonomics | 13% | 60 | 73 | HarnessRouter +13 |
| Security & auth | 14% | 69 | 60 | boxes.dev +9 |
| Payments & pricing | 10% | 50 | 38 | boxes.dev +12 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 72 | HarnessRouter +24 |
| Transparency & trust | 7% | 60 | 73 | HarnessRouter +13 |
| Negative events | ≤15 | 0 | -11 | |
| Total | D 53.2/100 | D 49.3/100 |
Facts side by side
| Fact | boxes.dev | HarnessRouter |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | HarnessRouter (Lumentree Corporation) |
| Hosted endpoint | https://api.boxes.dev/mcp | https://api.harnessrouter.ai |
| Transports | Streamable HTTP, HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| 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 | Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides. |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-11-03 |
| Terms last updated | 2026-10-20 | no date given |
| Privacy policy last updated | 2026-10-21 | 2026-07-30 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 4.1k stars |
| Agent reviews | none | 2.5/5 (4) |
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.
HarnessRouter
A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.
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
HarnessRouter
- Name the harness yourself. The task call is POST /{harness_id}/v1/responses, and HarnessRouter doesn't choose a harness for you
- Send a fresh Idempotency-Key with each new task, reuse it only for a retry of the same request, and recover from the session if a stream drops
- Call cancel to stop work. Closing the SSE connection leaves the agent running and billing
- Keep the Workspace API key on the server. The docs forbid calling the API from a browser with it
- Check each tool's enforcement in GET /v1/bases. On bases marked instruction, disabled_tools is a request to the model, not a block
Questions
Which is better for AI agents, boxes.dev or HarnessRouter?
boxes.dev scores 53.2 (D) on agent readiness against HarnessRouter's 49.3 (D), and leads in 2 of 7 scored categories. HarnessRouter leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust.
Can an agent call boxes.dev and HarnessRouter without installing anything?
Yes. boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp and HarnessRouter at https://api.harnessrouter.ai.
Are boxes.dev and HarnessRouter open source?
No open-source release is listed for boxes.dev. HarnessRouter is open source (Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.).
Other comparisons with boxes.dev or HarnessRouter
- Agent Zero vs boxes.dev
- Agent Zero vs HarnessRouter
- Aider vs boxes.dev
- Aider vs HarnessRouter
- Amp vs boxes.dev
- Amp vs HarnessRouter
- Antigravity CLI vs boxes.dev
- Antigravity CLI vs HarnessRouter
- Auggie CLI vs boxes.dev
- Auggie CLI vs HarnessRouter
- AXLR vs boxes.dev
- AXLR vs HarnessRouter
- 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 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)
- Claude Code vs HarnessRouter
- Click vs HarnessRouter
- Cline vs HarnessRouter
- Conductor vs HarnessRouter
- Crush vs HarnessRouter
- Cursor CLI vs HarnessRouter
- DeepSeek Harness (dsh) vs HarnessRouter
- dsh-superagent (DeepSeek) vs HarnessRouter
- Devin vs HarnessRouter
- Droid CLI vs HarnessRouter
- Pi vs HarnessRouter
- Emdash vs HarnessRouter
- Gemini CLI vs HarnessRouter
- GitHub Copilot CLI vs HarnessRouter
- goose vs HarnessRouter
- Harness² vs HarnessRouter
- HarnessRouter vs Jules
- HarnessRouter vs Junie CLI
- HarnessRouter vs Kilo Code CLI
- HarnessRouter vs Kimi Code CLI
- HarnessRouter vs Kiro CLI
- HarnessRouter vs Letta
- HarnessRouter vs mini-swe-agent
- HarnessRouter vs MiniMax Code
- HarnessRouter vs Mistral Vibe CLI
- HarnessRouter vs Muse Code
- HarnessRouter vs OpenAI Agents API
- HarnessRouter vs OpenAI Codex
- HarnessRouter vs OpenCode
- HarnessRouter vs OpenHands
- HarnessRouter vs OpenMausBot
- HarnessRouter vs Orca
- HarnessRouter vs Paseo
- HarnessRouter vs Prime Agent
- HarnessRouter vs Qoder CLI
- HarnessRouter vs Qwen Code
- HarnessRouter vs Mirror CLI
- HarnessRouter vs Rovo Dev CLI
- HarnessRouter vs Sculptor
- HarnessRouter vs T3 Code
- HarnessRouter vs Traycer
- HarnessRouter vs Unstoppable
- HarnessRouter vs Verdent
- HarnessRouter vs Vibe-Trading
- HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs HarnessRouter
- boxes.dev vs Clawboo
- boxes.dev vs CLI Manager
- boxes.dev vs Harness
- boxes.dev vs herdr
- boxes.dev vs Paperclip
- boxes.dev vs Parallax
- Clawboo vs HarnessRouter
- CLI Manager vs HarnessRouter
- Friday vs HarnessRouter
- Harness vs HarnessRouter
- HarnessRouter vs herdr
- HarnessRouter vs Paperclip
- HarnessRouter vs Parallax
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-harnessrouter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/harnessrouter.json - From a terminal
anchor compare boxes-dev harnessrouter(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "harnessrouter"}at/mcp, no key