Head to head · Multi-agent orchestration · October 2026 research run

boxes.dev vs herdr

herdr scores 71.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 multi-agent orchestration.

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 49

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, incident history or SLA found

herdr BB

Best for A developer who runs several coding agents in terminals, locally or over SSH, and wants one agent to start, prompt and wait on others.

Ahead on

  • Reliability, 65 against 32
  • Schema & documentation, 91 against 57
  • Agent ergonomics, 73 against 60
  • Payments & pricing, 90 against 50
  • Maintenance & community, 63 against 48
  • Transparency & trust, 70 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • Open source

Watch for

Version 0.9.5, not yet 1.0, and the last tagged release is 14 October 2026

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 herdr +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.

herdr 90

No payment protocol (0). Read with the self-hosted rule. herdr.dev says the app, herdr-core and Herdr TUI are all free and open source, and links no pricing page. Free (30), no card (30), and no account or signup at all (30). 0 + 30 + 30 + 30 = 90.

Schema & documentation herdr +34

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.

herdr 91

Read as a CLI and socket API. herdr api schema --json prints a JSON Schema for requests, responses, errors and events, also at docs/next/api/herdr-api.schema.json (25). Markdown for agents, with skills/herdr/SKILL.md and distribution/agent-guide.md. https://herdr.dev/llms.txt indexes the 0.9.5 docs as raw source files for agents (10). The skill says when to use herdr and when not to, and the socket docs say which layer to use for which job, but the schema itself carries few descriptions (15). The schema has 49 enums and agent names are constrained by a pattern, while some inputs are free strings (12). Many CLI and JSON examples, a documented error shape with codes such as not_found, agent_blocked and events_lost (14). Versioned docs per release and a changelog (15). 25 + 10 + 15 + 12 + 14 + 15 = 91.

Reliability herdr +33

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.

herdr 65

Read as local software, as for agents-tree and Harness. Official release binaries for Linux, macOS and Windows x86_64 with an install script, and Homebrew and mise in the README. The Homebrew formula wasn't read (20). .github/workflows/ci.yml runs checks and tests on ubuntu, macOS and Windows for every push and pull request, but run results couldn't be read from this session, so 15, the value this run gives public CI with unread results. 495 issues were open on 18 November 2026. The 25 newest, opened 15 to 18 November, all carry a triaged label and a priority (p1 or p2), several of them bugs, so reports are sorted within a day but many stay open (15). Semver tags and a Keep a Changelog file with Breaking Changes and Removed sections (15). Version 0.9.5, not 1.0, and not declared stable (0). 20 + 15 + 15 + 15 + 0 = 65.

Security & auth boxes.dev +20

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.

herdr 49

Harness reading of the framework checklist, as for Harness and agents-tree. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No account, no telemetry found in the source, and a socket file set to 0600. Version and manifest checks reach herdr.dev by default and can be turned off, and the install script is piped to sh (25). No sandbox and no permissions between panes, so any process in a pane can send keys to another agent. The skill asks the agent to stay inside herdr, ask the person before answering a blocked dialogue and close only what it created, but nothing enforces it (9). Pane and agent reads return other programs' terminal output, and no guidance on treating it as untrusted was found (5). A server log, but no per-call audit log found (5). No SECURITY.md or disclosure policy in the repository, and herdr.dev serves no security.txt. CI pins actions to commit SHAs and Dependabot is on (5). 25 + 9 + 5 + 5 + 5 = 49.

Maintenance & community herdr +15

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.

herdr 63

v0.9.5 on 14 October 2026, 35 days before the check, and the last commit on master on 29 October (20). Six releases from 7 September to 14 October 2026 (20). 495 open issues and 26 open pull requests. The 25 newest issues were labelled triaged with a priority within a day of opening. Unsolicited pull requests are closed automatically and a monthly workflow closes stale issues (15). Not an MCP server and no official SDK (0). Cargo.lock, Dependabot and CI on three systems, run results unread (8). 20 + 20 + 15 + 0 + 8 = 63.

Agent ergonomics herdr +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.

herdr 73

Framework reading, how much an agent has to carry. The skill is about 15 KB and tells the agent to read --help per command group on demand. Reads take --lines and --source recent (20 of 25). Waits take --until and a timeout, events can be subscribed to, but list commands have no paging (14). Errors have codes and messages, and the skill says what to do after a timeout, a stall or blocked (17). agent prompt --wait submits and waits in one request to avoid a race, agent.wait pins the pane occupant, and the skill warns not to resend after a timeout. No idempotency keys (14). Most commands default to the caller's or focused pane. No SDK, only the CLI and raw socket (8). 20 + 14 + 17 + 14 + 8 = 73.

Score by category

CategoryWeightboxes.devherdrEdge
Reliability16%3265herdr +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5791herdr +34
Agent ergonomics13%6073herdr +13
Security & auth14%6949boxes.dev +20
Payments & pricing10%5090herdr +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4863herdr +15
Transparency & trust7%6070herdr +10
Negative events≤1500
TotalD 53.2/100BB 71.1/100

Facts side by side

Factboxes.devherdr
KindMCP serverAgent harness
VendorBoxes, Inc.herdr
Hosted endpointhttps://api.boxes.dev/mcpno (local only)
TransportsStreamable HTTP, HTTP
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceProprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSEDApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-14
Terms last updated2026-10-20no document linked
Privacy policy last updated2026-10-212026-11-02
Customer content may train modelsnot found in the textnot read yet
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
Popularitynone52k stars

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.

herdr

Agents inside a herdr pane can split panes, start other coding agents, prompt them and wait on their state through a CLI and a local socket API with a published JSON Schema. It is pre-1.0 local software with no sandbox, and any process in a pane can type into another agent's terminal.

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

herdr

  1. Check HERDR_ENV=1 before any herdr command. If it isn't set, tell the person you aren't inside herdr and stop
  2. Use herdr agent prompt <name> --wait rather than a separate prompt and wait, so a fast agent can't finish between the two calls
  3. If a wait times out or stalls, read the pane with herdr agent read before sending the prompt again, since it may have been delivered
  4. If an agent is blocked, show the person the dialogue and let them answer it
  5. Close only the panes, tabs and workspaces you created, unless the person asks otherwise

Questions

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

herdr scores 71.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 herdr without installing anything?

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

Are boxes.dev and herdr open source?

No open-source release is listed for boxes.dev. herdr is open source (Apache-2.0).

Other comparisons with boxes.dev or herdr

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.