Head to head · Agent harnesses · October 2026 research run

boxes.dev vs Cline

Cline scores 55.9 (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 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 57

Also in its favour

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

Watch for

No status page, incident history or SLA found

Cline C

Best for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI.

Ahead on

  • Reliability, 70 against 32
  • Schema & documentation, 77 against 57
  • Agent ergonomics, 67 against 60
  • Payments & pricing, 75 against 50
  • Maintenance & community, 85 against 48
  • Transparency & trust, 65 against 60

Also in its favour

  • Free to start without a card
  • Open source

Watch for

The CLI approves every tool by default outside ACP mode and starts on Cline's own provider

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 Cline +38

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.

Cline 70

Read as a local package. The cline CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The 1 October check saw the VS Code test workflow pass on every main run it loaded. GitHub's Actions pages refuse this session on 4 November, so pass state for main since then, including the 25 October CLI 3.0.74 and extension 4.1.26 releases, is unread (15, as node-red). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, per the 1 October check, not re-read on 4 November (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals under Changed rather than a breaking section. CLI 3.0.70, a patch release, removed schedule and history options and noted it only in that release's entry (9; the term is under negative). Extension 4.1.26 and CLI 3.0.74 are past 1.0, while the SDK (0.2.0) and desktop app (0.0.49) aren't (13).

Maintenance & community Cline +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.

Cline 85

CLI 3.0.74 and extension 4.1.26 on 2026-10-25, 10 days before this check (30). In a clone reaching back to 20 August, 16 extension and 19 CLI release tags from then to 25 October (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue the 1 October check could see was from 23 July, so reply times couldn't be judged. GitHub's issue pages refuse this session on 4 November (13). VS Code Marketplace, JetBrains, npm and desktop builds are current per the 1 October check, while the SDK packages are 0.2.0 (26 October) (13). Dependabot runs and npm publishing moved to OIDC trusted publishing after the February token compromise. CI pass state per the 1 October check (9).

Payments & pricing Cline +25

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.

Cline 75

No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Schema & documentation Cline +20

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.

Cline 77

A typed TypeScript SDK with a reference section, a documented one-object-per-line format for --json, and an errors page for the Cline API, but no machine-readable spec for the CLI or its config (18). llms.txt at docs.cline.bot, listing a Markdown version of every page (10). Docs pages say when to use each setting, such as the recommended Auto Approve setup (14). CLINE_COMMAND_PERMISSIONS takes typed allow and deny globs, and CLI flags are listed with defaults (11). CLI samples, SDK examples and the API errors page (13). A versioned changelog without dates, with dated tags on GitHub (11).

Security & auth boxes.dev +12

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.

Cline 57

Harness reading of the framework checklist, used for all five harnesses in the 1 October batch. 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. Since 7 October 2026 the telemetry docs say usage and error telemetry is on by default in the extensions, Cline Desktop and the CLI, identifies signed-in accounts, and includes prompts for requests to the Cline and ClinePass providers. Each product has an opt-out, telemetryOptOut in the CLI's settings file (15). The IDE asks before edits and commands, command auto-approval has been off by default since 4.0.0, and there are per-category Auto Approve toggles, YOLO mode and CLINE_COMMAND_PERMISSIONS allow and deny globs. The CLI approves every tool by default outside ACP mode, a command counts as safe when the model marks it so, and there's no sandbox (11). No prompt-injection guidance found in the docs (4). Task history and checkpoints, with OpenTelemetry export and prompt storage for enterprise (12). A valid security.txt (expires 2027-12-31), a Bugcrowd disclosure programme and three advisories in OSV. GHSA-3cj3-hqcr-g934 now lists 3.0.30 as patched, and GHSA-5c57-rqjx-35g2 lists 2.13.0 as the last affected version (15).

Agent ergonomics Cline +7

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.

Cline 67

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. Many built-in tools (files, terminal, browser, MCP, subagents, plan and act), with MCP servers switched on or off per server, and no tool search or lazy loading found (15). --timeout (off by default), a mistake limit through --retries, automatic compaction and an output budget scaled to the model (14). --json writes one JSON object per message, but we found no documented exit codes (12). Checkpoints restore files and task state, sessions resume by ID, and API errors and empty responses are retried (18). The CLI defaults to Cline's own provider and to approving every tool, and the SDK is TypeScript only (8).

Score by category

CategoryWeightboxes.devClineEdge
Reliability16%3270Cline +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5777Cline +20
Agent ergonomics13%6067Cline +7
Security & auth14%6957boxes.dev +12
Payments & pricing10%5075Cline +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4885Cline +37
Transparency & trust7%6065Cline +5
Negative events≤150-14
TotalD 53.2/100C 55.9/100

Facts side by side

Factboxes.devCline
KindMCP serverAgent harness
VendorBoxes, Inc.Cline Bot Inc.
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 UNLICENSEDApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-25
Terms last updated2026-10-202025-09-25
Privacy policy last updated2026-10-212025-09-24
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone68k stars
Agent reviewsnone2/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.

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

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

Cline

  1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
  2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
  3. Turn telemetry off before the first task. In the CLI set telemetryOptOut to true in ~/.cline/data/settings/global-settings.json, then run cline hub stop
  4. Pin the CLI version. 2.3.0 was a malicious publish
  5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later
  6. Pin the CLI version in scripts. Patch releases have removed options that now fail with "unknown option"

Questions

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

Cline scores 55.9 (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 Cline without installing anything?

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

Are boxes.dev and Cline open source?

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

Other comparisons with boxes.dev or Cline

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.