Head to head · Agent harnesses · October 2026 research run

Agent Zero vs boxes.dev

boxes.dev scores 53.2 (D) on agent readiness against Agent Zero's 49.7 (D), and leads in 1 of 7 scored categories. Agent Zero leads on reliability, schema & documentation, payments & pricing and maintenance & community. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Agent Zero D

Best for A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory.

Ahead on

  • Reliability, 57 against 32
  • Schema & documentation, 64 against 57
  • Payments & pricing, 90 against 50
  • Maintenance & community, 75 against 48

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No approval step before shell commands, file changes or outgoing messages. Tool Access defaults to allow

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 54

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Agent Zero loses 15 points for them

Watch for

No status page, incident history or SLA found

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 Agent Zero +40

Agent Zero 90

Read with the self-hosted rule. No payment protocol in the source (0). Free under MIT with nothing to buy for the software, so 20, 20 and 20 on the last three lines. It starts with one Docker command and no account. Model usage is billed by whichever provider the owner configures, or costs nothing with a local model. The vendor's site also describes a beta LLM API whose daily quota depends on staking its A0T token. That is separate from the software and not scored. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

Maintenance & community Agent Zero +27

Agent Zero 75

v2.15 was tagged on 1 November 2026, 3 days before this check (30). Seven releases from 6 August, v2.9 on 12 August to v2.15, read from the clone's tags (20). Of the 40 newest open items read on 12 October, 16 are issues and 14 of those have no comment. Three security reports filed as issues were closed as completed, one in five days and two after three months. GitHub's issue pages weren't read on 4 November, so this is per the 12 October check (10 of 25). The Docker image, the desktop Launcher, the install scripts and the A0 CLI connector come from the same organisation, and the v2.14 notes point the README's Launcher links to v1.9 (10 of 15). A Docker publish workflow builds images from tags, and the v2.14 notes raise dependency security floors for aiohttp, anyio, urllib3, filelock, fsspec and multidict. No public test CI (5 of 10). 30 + 20 + 10 + 10 + 5 = 75.

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.

Reliability Agent Zero +25

Agent Zero 57

Read with the local-software lines, as software the owner runs. Installs from the agent0ai/agent-zero Docker image, an install script, or a desktop Launcher with builds for macOS, Linux and Windows on x86 and ARM64. The README says it runs wherever Docker runs. The image registry page was not read (17 of 20). The repository holds 245 files under tests/ on 4 November, and its only two workflows still publish Docker images and close inactive issues. The publish workflow runs no tests, so no public CI run shows them passing (5 of 25, a partial kept). 139 open issues and pull requests on 12 October 2026, per that check (GitHub's pages and API weren't read on 4 November). Open reports from September include a crash of run_ui after a failed memory consolidation (#1909), a browser worker that hangs the agent turn (#1923) and truncated backups (#1904), each with no reply or one, and a workflow closes anything inactive for 90 days (11 of 25). Release notes for v2.11, v2.12 and v2.13 carry a Breaking Changes section, but breaking changes ship in minor versions, so the numbering is not semver (9 of 15). v2.15, past 1.0 (15).

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.

Security & auth boxes.dev +15

Agent Zero 54

Harness reading of the framework checklist, the one the Goose calibration dossier uses. 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. No usage telemetry was found in the source. An update check, on by default, posts the version and a 20-character SHA-256 hash of a random per-install id to api.agent-zero.ai. The Update Checker settings page says only that ID and the version are sent and has an off switch. Something still leaves the machine by default, so the partial is kept (22). The agent works inside a Docker container built on Kali Linux and runs as root there. Tool Access can block tools by project or profile and defaults to allow, host access through the A0 CLI is scoped by read, write and execute permissions, and no approval step was found before a shell command, a file deletion or an outgoing message. The web interface has no login until a username is set (10). Infection Check audits the agent's reasoning with a second model before each tool call and ships disabled. Scanners check plugins, skills and MCP servers before install. The channel allow-lists accept every sender when empty, and the email filter matches the claimed From address only, which the plugin README states (7). Chat logs, visible tool steps and Time Travel snapshots, with no per-call audit log. Per-process log files were removed in v2.5 (9). No SECURITY.md on 4 November, security.txt answered 404 on 12 October, and none of the eight CVEs published from 17 March to 22 October 2026 came from the vendor (VulDB, VulnCheck, MITRE and CISA assigned them). A security-review ledger in the repository records two findings, and the v2.12 notes name both fixes (6, a partial kept).

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.

Schema & documentation Agent Zero +7

Agent Zero 64

Harness reading of the lines, as the Goose calibration dossier does. No OpenAPI file. The connectivity page lists five external endpoints and the X-API-KEY header, then sends readers to the source or DeepWiki for request and response details. Each API handler and tool has a .dox.md contract file in the repository, and the MCP client JSON shape is documented (10 of 25). llms.txt at www.agent-zero.ai, and AGENTS.md contract files across the repository (10). Guides say which path to use for a need, with tables that separate the browser, the host connector, MCP and A2A (14 of 20). The v2.12 notes say 15 bundled tools gained argument descriptions in non-strict schemas, and plugin settings are typed YAML with commented examples (8 of 15). Guides carry worked examples and a troubleshooting page, with no documented error responses for the external API (9 of 15). Dated notes on every GitHub release and a release article for each version on the site, with no version prefix on API routes (13 of 15).

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.

Score by category

CategoryWeightAgent Zeroboxes.devEdge
Reliability16%5732Agent Zero +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6457Agent Zero +7
Agent ergonomics13%6260Agent Zero +2
Security & auth14%5469boxes.dev +15
Payments & pricing10%9050Agent Zero +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7548Agent Zero +27
Transparency & trust7%6460Agent Zero +4
Negative events≤15-150
TotalD 49.7/100D 53.2/100

Facts side by side

FactAgent Zeroboxes.dev
KindAgent harnessMCP server
VendorAgent Zero, s.r.o.Boxes, Inc.
Hosted endpointno (local only)https://api.boxes.dev/mcp
TransportsStreamable HTTP, HTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITProprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSED
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-012026-11-17
Terms last updatedno document linked2026-10-20
Privacy policy last updatedno document linked2026-10-21
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity19k starsnone

How the scores have moved

Verdicts

Agent Zero

Self-hosted under the MIT licence, with seven releases from 12 August to 1 November 2026 and breaking changes listed in minor-release notes. The agent runs shell commands in its container with no approval step, the web interface has no login by default, and eight CVEs from the past year were published by third parties with no vendor advisory.

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.

Before you call either

Agent Zero

  1. Set a UI login and password in Settings before publishing the port or opening a tunnel. The default has none
  2. Fill allowed_users, allowed_numbers or sender_whitelist before enabling a channel. An empty list accepts every sender
  3. Enable the Infection Check plugin when the agent reads mail, web pages or MCP results. It ships disabled
  4. Run v2.12 or later. It fixes a Telegram webhook authentication bypass and a WhatsApp media path traversal
  5. Call POST /api_message with the X-API-KEY header. The token changes when the UI login or password changes

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

Questions

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

boxes.dev scores 53.2 (D) on agent readiness against Agent Zero's 49.7 (D), and leads in 1 of 7 scored categories. Agent Zero leads on reliability, schema & documentation, payments & pricing and maintenance & community.

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

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

Are Agent Zero and boxes.dev open source?

Agent Zero is open source (MIT). No open-source release is listed for boxes.dev.

Other comparisons with Agent Zero or boxes.dev

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.