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

boxes.dev vs Paperclip

Paperclip scores 56.4 (C) 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 64

Also in its favour

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

Watch for

No status page, incident history or SLA found

Paperclip C

Best for Someone running several coding or operations agents who wants one place for tasks, budgets, approvals and history across harnesses.

Ahead on

  • Reliability, 59 against 32
  • Schema & documentation, 81 against 57
  • Agent ergonomics, 70 against 60
  • Payments & pricing, 90 against 50
  • Maintenance & community, 78 against 48
  • Transparency & trust, 66 against 60

Also in its favour

  • Free to start without a card
  • Open source

Watch for

claude_local defaults dangerouslySkipPermissions to true and codex_local defaults to bypassing approvals and the sandbox, with agents running on the host

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

Paperclip 90

No payment protocol (0). Read with the self-hosted rule. The software is free under MIT with nothing to buy (20). No card and no Paperclip account (20). One npx command installs and starts it with no signup (20). Paperclip Cloud is a waitlist with no published price, so there is no paid option to score. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Paperclip +30

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.

Paperclip 78

Version 2026.1023.0, released on 23 October 2026 per its notes and the site banner (30). Ten stable releases from 2026.817.0 (17 August) to 2026.1023.0 in the 90 days to 4 November (20). Per the 8 October check, not re-read on 4 November, 650 pull requests merged in the last 30 days, but 2,849 issues and 3,338 pull requests were open, 1,396 open issues had no comment, and 309 of the 472 still-open issues from the two weeks before had none (8). paperclipai and @paperclipai/mcp-server publish from the same release workflow. We did not check the MCP registry (12). CI on master, a lockfile refresh workflow and signed image attestations (8). 30 + 20 + 8 + 12 + 8 = 78.

Reliability Paperclip +27

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.

Paperclip 59

Read as local software. Official npm package paperclipai (Node.js 24.11 or newer) and a Docker image on GHCR (20). Public CI that runs the tests (pr-trusted.yml selects and runs the test shards, and e2e.yml runs the end-to-end suite), with the pass state on master unreadable on 4 November 2026 because GitHub's pages answer 403 here (15). Per the 8 October check, not re-read on 4 November, 2,849 open issues, 125 labelled bug, 1,599 opened before 8 July, and 78 closed in the last 30 days against 686 opened (6). Calendar versions in semver syntax, with a Breaking Changes section and an upgrade guide in release notes, but breaking changes arrive in ordinary releases and 2026.916.0 carried five (10). No 1.0. The npm latest tag is called the stable channel and follows a beta soak of at least three days, while the roadmap says the product is still moving quickly, so half credit (8). 20 + 15 + 6 + 10 + 8 = 59.

Schema & documentation Paperclip +24

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.

Paperclip 81

The running server publishes OpenAPI at /api/openapi.json and validates requests with Zod, and the MCP server's tools take Zod schemas. No copy of the spec is published on the docs site, and paperclip.ing/openapi.json describes only the website (22). llms.txt at paperclip.ing, and docs pages answer as Markdown at .md (10). An API reference page per resource and task guides, but the MCP tool descriptions are one line each, such as List agents in a company (13). Typed inputs throughout, apart from the paperclipApiRequest tool, which takes any path under /api and a JSON body (12). cURL, JavaScript and Python examples and a status-code table, with one {error} shape and an occasional details field (12). A changelog page for every stable release and release notes in the repository, but the API path carries no version (12).

Agent ergonomics Paperclip +10

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.

Paperclip 70

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The MCP server lists 44 tools with no toolsets or read-only subset found, offset by compact reads such as paperclipInboxLite and the heartbeat context (12). Budgets by company, agent and project with an automatic pause at 100 per cent, though the README says enforcement uses recorded spend and can lag work in flight (16). onboard --yes, CLI commands with --json, the REST API and routines started by cron, webhook or API (16). Atomic task checkout with a documented 409, Idempotency-Key on routine triggers, saved sessions and bounded recovery (17). One command starts a server with embedded PostgreSQL, but it needs Node.js 24.11 and each harness CLI installed and signed in on the host, and we found no client SDK beyond the TypeScript plugin SDK (9).

Transparency & trust Paperclip +6

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.

Paperclip 66

MIT (30). The privacy policy of 23 July 2026 separates self-hosted use from the hosted services and names Paperclip Labs, Inc., but keeps data as long as reasonably necessary, lists no subprocessors, and the 90-day telemetry retention appears only in source. The terms grant a broad licence over content sent to the services and allow model training on opt-in detailed telemetry (16). Release notes carry dated Breaking Changes sections and upgrade guides, with no written deprecation policy or notice period (10). The README discloses telemetry, what it excludes and four opt-outs, and the event contract is public in the repository, but it is on by default (17).

Score by category

CategoryWeightboxes.devPaperclipEdge
Reliability16%3259Paperclip +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5781Paperclip +24
Agent ergonomics13%6070Paperclip +10
Security & auth14%6964boxes.dev +5
Payments & pricing10%5090Paperclip +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4878Paperclip +30
Transparency & trust7%6066Paperclip +6
Negative events≤150-15
TotalD 53.2/100C 56.4/100

Facts side by side

Factboxes.devPaperclip
KindMCP serverAgent harness
VendorBoxes, Inc.Paperclip Labs, Inc.
Hosted endpointhttps://api.boxes.dev/mcpno (local only)
TransportsStreamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFree
x402nono
LicenceProprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSEDMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-23
Terms last updated2026-10-202026-07-23
Privacy policy last updated2026-10-212026-07-23
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone99k stars, 60k npm/wk

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.

Paperclip

Board approvals, budgets with a hard stop and an activity log sit above whichever harnesses do the work, with ten stable versions in 90 days. The Claude Code and Codex adapters skip permission prompts and the sandbox by default, twelve security advisories have appeared since April 2026, and a 24 October cross-company read fix is in no stable release.

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

Paperclip

  1. Set PAPERCLIP_TELEMETRY_DISABLED=1 or DO_NOT_TRACK=1 before the first start. Telemetry is on by default
  2. Set dangerouslySkipPermissions and dangerouslyBypassApprovalsAndSandbox to false on agents that read untrusted input, or run them in a sandbox provider
  3. Install with Node.js 24.11 or newer, and install and sign in to each harness CLI on the host first. Paperclip assumes they are there
  4. Use --bind lan or --bind tailnet at onboarding for anything beyond one machine. The default local_trusted mode treats every request as the board admin
  5. Treat 409 on task checkout as owned by another agent and pick different work. The API docs say not to retry

Questions

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

Paperclip scores 56.4 (C) 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 Paperclip without installing anything?

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

Are boxes.dev and Paperclip open source?

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

Other comparisons with boxes.dev or Paperclip

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.