Head to head · Agent harnesses · October 2026 research run

boxes.dev vs OpenHands

OpenHands scores 74.1 (BB) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories. boxes.dev leads on security & auth. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

boxes.dev D

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 64

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where OpenHands loses 7 points for them

Watch for

No status page, incident history or SLA found

OpenHands BB

Best for Teams that want to self-host a coding agent with a web UI, per-conversation Docker sandboxes and scheduled or webhook automations, or embed the agent through a Python SDK and REST API.

Ahead on

  • Reliability, 90 against 32
  • Schema & documentation, 90 against 57
  • Agent ergonomics, 78 against 60
  • Payments & pricing, 90 against 50
  • Maintenance & community, 85 against 48
  • Transparency & trust, 67 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Confirmation mode is off by default in Agent Canvas, and the npm install gives the agent the host's whole filesystem

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.

Reliability OpenHands +58

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.

OpenHands 90

Read as a local package. Official npm package @openhands/agent-canvas (Node 24 or later, plus uv), a Docker image on GHCR and openhands-sdk on PyPI (Python 3.12 or later) (20). A CI workflow (ci.yml) runs on main beside desktop, Docker and end-to-end workflows; the runs passed on every load on 1 October, and GitHub's pages refused us on 1 November, so the award rests on that check (25). 456 open issues and 395 open pull requests with priority labels and a high-priority Cloud resume bug (#17664), per the 1 October check, not re-read on 1 November (18). Dated release notes for every Canvas version and a written SDK rule of at least five minor releases before a public API or REST contract is removed, which the SDK followed on 28 October when it dropped the ACP curated model lists at their stated 1.59.0 deadline, but the Canvas CHANGELOG.md still stops at 1.0.0-alpha.2 (12). Canvas is 1.34.0 and the SDK 1.59.0, and the README's beta badge was removed on 23 October 2026 (commit 4d1c4d1, noted in the 1.33.0 release notes), so the product is no longer labelled beta. Only the Apps extension API keeps a beta label (15).

Payments & pricing OpenHands +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.

OpenHands 90

No payment protocol (0). Scored on the paid options and the OpenHands LLM provider. The docs publish per-token prices for the OpenHands LLM provider at provider rates with no markup, and the pricing page now lists Agent Canvas free, Teams at $500 a month for up to 10 users (plus $50 a seat, 30-day trial) and Enterprise by sales (20). The MIT stack is free to self-host, and two DeepSeek models are free on app.all-hands.dev (20). It runs any model through LiteLLM, local ones included, so an agent can install and run it with no signup (20). The provider price table still lists 2025 models, so it may be stale. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community OpenHands +37

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.

OpenHands 85

Agent Canvas 1.34.0 on 2026-10-27 and SDK 1.59.0 on 2026-10-28, by the repository tags (30). 29 Canvas releases (1.9.0 on 3 August to 1.34.0) and 33 SDK releases (1.40.1 on 5 August to 1.59.0) in the 90 days from 3 August, not counting the security rebuild tags (20). Issues labelled by priority, but 456 open issues and 395 open pull requests and no visible reply times per the 1 October check; GitHub's pages refused us on 1 November (16). npm, PyPI and GHCR packages current per the 1 October check (the registries didn't answer from our shell on 1 November). The unmaintained openhands CLI is gone from the docs navigation and the pricing page but its pages remain (10). CI on main, Dependabot, a security scan and an API-breakage check on the SDK, and security rebuilds of older images (agent-canvas 1.23.0-r3, agent-server 1.49.5-r3, 29 October) (9).

Schema & documentation OpenHands +33

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.

OpenHands 90

The Agent Server REST API has an OpenAPI 3.1 spec in the docs repository (40 paths, still labelled 0.1.0), the Cloud API has another (155 paths), SDK models are Pydantic-typed and there's a TypeScript client (25). llms.txt at docs.openhands.dev (551 lines on 1 November), with no CLI, local GUI or V0 pages in it (10). The docs have a when-to-use page and examples of good and bad task instructions. On 23 October the Deprecated Projects group (local GUI, CLI, V0) was taken out of the navigation and links to it reworded towards Agent Canvas, though the pages stay reachable by URL and the SDK architecture page still links the CLI repository (15). Confirmation policies, security analysers and MCP configs are discriminated Pydantic unions with validators (13). SDK examples are checked by a CI workflow and there are troubleshooting pages, but we found no error reference for the Agent Server (12). Dated release notes for each Canvas version in the docs (1.25.0 to 1.34.0 added since 1 October), and release tags (15).

Agent ergonomics OpenHands +18

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.

OpenHands 78

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The default agent carries three tools (terminal, file editor, task tracker), and filter_tools_regex trims MCP tools before they reach the model (23). Stuck detection is on by default and a condenser compacts long histories, but Canvas leaves max_iterations unset and we found no cost cap (15). Headless runs go through the SDK, the Agent Server REST API or the Cloud API with typed events, and the old CLI's --headless mode is unmaintained (14). Conversations persist and resume, and a Docker conversation keeps its workspace and history when the container is replaced (16). Python SDK and TypeScript client, but the quickstart needs Node 24 and uv, and the defaults skip both confirmation and the sandbox (10).

Transparency & trust OpenHands +7

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.

OpenHands 67

MIT across Canvas, SDK, tools and Agent Server (30). The privacy policy (effective 3 September 2025, re-read on 1 November) doesn't separate the open-source stack from the Cloud service, keeps data as long as reasonably necessary, allows training on content from the Services and has no subprocessor list (12). A written SDK deprecation runway of five minor releases, kept on 28 October when the ACP model lists were removed at their 1.59.0 deadline, and the CLI's unmaintained notice in its README without a date on the page (15). The consent prompt calls the data anonymous and the Docker page documents AGENT_CANVAS_DISABLE_TELEMETRY, but no user-facing page mentions the install event sent before consent (10).

Score by category

CategoryWeightboxes.devOpenHandsEdge
Reliability16%3290OpenHands +58
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5790OpenHands +33
Agent ergonomics13%6078OpenHands +18
Security & auth14%6964boxes.dev +5
Payments & pricing10%5090OpenHands +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4885OpenHands +37
Transparency & trust7%6067OpenHands +7
Negative events≤150-7
TotalD 53.2/100BB 74.1/100

Facts side by side

Factboxes.devOpenHands
KindMCP serverAgent harness
VendorBoxes, Inc.All Hands AI
Hosted endpointhttps://api.boxes.dev/mcpno (local only)
TransportsStreamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSEDMIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted service
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-28
Terms last updated2026-10-20no document linked
Privacy policy last updated2026-10-212025-09-03
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone90k stars
Agent reviewsnone2.5/5 (2)

How the scores have moved

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.

OpenHands

A self-hosted coding agent with a typed SDK, an Agent Server API and a Docker container per conversation on request. Agent Canvas still starts with confirmation off on the host's filesystem, sends an install event before asking consent, and a critical SDK sandbox flaw fixed in October was published by a third party.

Before you call either

boxes.dev

  1. Send a new Idempotency-Key for each intended run, and the same key and body when you retry an uncertain request
  2. Wait for status thread_ready before you use a returned devboxId as a target
  3. If you get 409 active_fork_limit_reached, free an awake devbox or wait. The plan's awake-devbox cap is full
  4. Read the thread in boxes.dev for the agent's answer. The status URL does not return it
  5. Ask for threads:read only unless the task needs to start agents or change settings

OpenHands

  1. Set AGENT_CANVAS_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 before the first start
  2. Start Canvas with OH_CONVERSATION_RUNTIME=docker or use the Docker image. The npm install runs the agent on the host
  3. Turn on confirmation mode with a risk threshold. Canvas starts with it off
  4. Pin openhands-sdk and openhands-workspace at 1.52.0 or later so DockerWorkspace binds to loopback, and set OH_SESSION_API_KEYS_0 on any reachable Agent Server
  5. Use the SDK or the Agent Server API for headless runs. The openhands --headless CLI is no longer maintained

Questions

Which is better for AI agents, boxes.dev or OpenHands?

OpenHands scores 74.1 (BB) on agent readiness against boxes.dev's 53.2 (D), and leads in 6 of 7 scored categories. boxes.dev leads on security & auth.

Can an agent call boxes.dev and OpenHands without installing anything?

boxes.dev has a hosted endpoint at https://api.boxes.dev/mcp. No hosted endpoint is listed for OpenHands.

Are boxes.dev and OpenHands open source?

No open-source release is listed for boxes.dev. OpenHands is open source (MIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted service).

Other comparisons with boxes.dev or OpenHands

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.