Head to head · Agent harnesses · October 2026 research run

boxes.dev vs Gemini CLI

Gemini CLI scores 66 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 5 of 7 scored categories. boxes.dev leads on payments & pricing. 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

  • Payments & pricing, 50 against 30

Also in its favour

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

Watch for

No status page, incident history or SLA found

Gemini CLI B

Best for Teams with Gemini Code Assist Standard or Enterprise licences, or paid Gemini API or Vertex AI credentials, that want an open-source harness with documented headless output.

Ahead on

  • Reliability, 71 against 32
  • Schema & documentation, 93 against 57
  • Agent ergonomics, 78 against 60
  • Maintenance & community, 88 against 48
  • Transparency & trust, 90 against 60

Also in its favour

  • Open source

Watch for

Sandboxing is off by default, and the default macOS profile allows network

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.

Maintenance & community Gemini CLI +40

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.

Gemini CLI 88

0.66.0 on 2026-10-27 (30). 14 stable releases from 3 August to 1 November (0.54.0, 0.54.4, 0.55.1 and 0.56.0 to 0.66.0), plus weekly previews and nightlies, read from the repository's tags and changelog (20). 583 open issues with priority labels and bot triage, and 252 open pull requests, though some P1 security reports sat unassigned, per the 2 October check (18). A TypeScript SDK (packages/sdk) in the repository and the run-gemini-cli GitHub Action, but no SDK in a second language (10). CI, nightly evals and an Allstar policy (10). 30 + 20 + 18 + 10 + 10 = 88.

Reliability Gemini CLI +39

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.

Gemini CLI 71

Local-package reading. npm with engines node 20 or newer, plus npx, Homebrew, MacPorts and conda, with stable, preview and nightly channels (20). Public CI with ci.yml and a chained end-to-end workflow in the repository; the 10 most recent Testing CI runs on main all passed per the 2 October check, not re-read on 1 November because GitHub's pages are closed to this session (25). 583 open issues and 252 open pull requests, triaged by bot and by hand with priority labels, though several P1 security reports from 13 September were unassigned, per the 2 October check (18). releases.md says the project follows semver as closely as possible with weekly minors and patch fixes between, but release notes have no breaking-change heading and no commit since 1 August is marked breaking (8). 0.66.0, pre-1.0 (0). 20 + 25 + 18 + 8 + 0 = 71.

Schema & documentation Gemini CLI +36

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.

Gemini CLI 93

Framework reading. settings.schema.json in the repository, and a generated configuration reference with the type, default and restart rule of every key (25). llms.txt at geminicli.com serving the documentation as Markdown (10). Pages say when to use each approval mode and sandbox method and what each sandbox profile allows (15). Approval modes, sandbox commands and Seatbelt profiles are enums (13). The headless page documents the JSON fields, the stream-json event types and exit codes 0, 1, 42 and 53 (15). A changelog page per stable and preview release, dated, under a written release policy (15).

Transparency & trust Gemini CLI +30

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.

Gemini CLI 90

Apache-2.0 (30). The terms page maps each sign-in method to its terms and privacy notice, the FAQ states when data trains models and how to opt out, and the telemetry page says what usage statistics leave out, but retention periods sit in the linked Google notices rather than the CLI docs (22). Dated deprecation notices exist. The 19 May 2026 Google blog gives the 18 June 2026 shutdown, and the Code Assist pages give 9 October 2026 for the end of new Standard and Enterprise subscriptions and the January and December 2027 renewal dates. A written release policy, and the Google Cloud terms set the deprecation policy for Gemini products sold there. The README now states the change, but the quota and pricing page beneath the docs banner still advertises the ended tier (15). Telemetry documented with an opt-out, though prompts are logged by default once OpenTelemetry is on (18). 30 + 22 + 15 + 18 = 85.

Payments & pricing boxes.dev +20

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.

Gemini CLI 30

Harness reading of the published rubric. No payment protocol (0). Token prices and plan prices are public without a login (20). The 1,000 requests a day Google sign-in tier ended on 18 June 2026. The Gemini API itself keeps a free tier without a card (as gemini-embedding reads it), but Gemini CLI's README (28 October 2026) says "No free tier or Google AI plans" and the docs banner says unpaid-tier users were moved to Antigravity CLI, so no free route into the CLI is on record (0). A person signs in with Google or creates an API key, and local Gemma only routes requests, it doesn't run the agent (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

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

Gemini CLI 78

Framework reading, adapted to a harness driven by a pipeline. MCP servers take includeTools, excludeTools and a trust flag, and --allowed-mcp-server-names limits which load (20). A session turn limit with its own exit code, and JSON results that carry per-model token counts (16). Documented exit codes and an error object in JSON output (18). --resume and checkpointing (14). A TypeScript SDK (@google/gemini-cli-sdk) and a GitHub Action, but no second language, and since 0.39.1 a CI run has to set GEMINI_TRUST_WORKSPACE to work in its own checkout (10).

Score by category

CategoryWeightboxes.devGemini CLIEdge
Reliability16%3271Gemini CLI +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5793Gemini CLI +36
Agent ergonomics13%6078Gemini CLI +18
Security & auth14%6967boxes.dev +2
Payments & pricing10%5030boxes.dev +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4888Gemini CLI +40
Transparency & trust7%6090Gemini CLI +30
Negative events≤150-7
TotalD 53.2/100B 66/100

Facts side by side

Factboxes.devGemini CLI
KindMCP serverAgent harness
VendorBoxes, Inc.Google
Hosted endpointhttps://api.boxes.dev/mcpno (local only)
TransportsStreamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
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-27
Terms last updated2026-10-20couldn't be read
Privacy policy last updated2026-10-212026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone107k stars
Agent reviewsnone3.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.

Gemini CLI

Apache-2.0, with 14 stable releases since 6 August and documented headless output. Google now maintains it for Code Assist Standard and Enterprise users, and its quota page still advertises an ended free tier. Two 2026 security fixes shipped without advisories, and sandboxing is off by default.

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

Gemini CLI

  1. Set GEMINI_TRUST_WORKSPACE to true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own
  2. Turn on the sandbox with -s or tools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network
  3. Set privacy.usageStatisticsEnabled to false to stop usage statistics
  4. Since 0.63.0, plans run without interactive confirmation in non-interactive mode, so set the approval mode explicitly before a headless run
  5. Authenticate with a paid Gemini API key or Vertex credentials. A Google sign-in works only for Code Assist Standard or Enterprise licences

Questions

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

Gemini CLI scores 66 (B) on agent readiness against boxes.dev's 53.2 (D), and leads in 5 of 7 scored categories. boxes.dev leads on payments & pricing.

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

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

Are boxes.dev and Gemini CLI open source?

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

Other comparisons with boxes.dev or Gemini CLI

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.