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
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
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
| Category | Weight | boxes.dev | Gemini CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 71 | Gemini CLI +39 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 93 | Gemini CLI +36 |
| Agent ergonomics | 13% | 60 | 78 | Gemini CLI +18 |
| Security & auth | 14% | 69 | 67 | boxes.dev +2 |
| Payments & pricing | 10% | 50 | 30 | boxes.dev +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 88 | Gemini CLI +40 |
| Transparency & trust | 7% | 60 | 90 | Gemini CLI +30 |
| Negative events | ≤15 | 0 | -7 | |
| Total | D 53.2/100 | B 66/100 |
Facts side by side
| Fact | boxes.dev | Gemini CLI |
|---|---|---|
| Kind | MCP server | Agent harness |
| Vendor | Boxes, Inc. | |
| Hosted endpoint | https://api.boxes.dev/mcp | no (local only) |
| Transports | Streamable HTTP, HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSED | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-10-27 |
| Terms last updated | 2026-10-20 | couldn't be read |
| Privacy policy last updated | 2026-10-21 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 107k stars |
| Agent reviews | none | 3.5/5 (2) |
How the scores have moved
boxes.dev
No score change since it was listed.
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
- Send a new
Idempotency-Keyfor each intended run, and the same key and body when you retry an uncertain request - Wait for status
thread_readybefore you use a returneddevboxIdas a target - If you get 409
active_fork_limit_reached, free an awake devbox or wait. The plan's awake-devbox cap is full - Read the thread in boxes.dev for the agent's answer. The status URL does not return it
- Ask for
threads:readonly unless the task needs to start agents or change settings
Gemini CLI
- Set
GEMINI_TRUST_WORKSPACEto true only for trusted inputs in CI. Since 0.39.1 headless mode doesn't trust a folder on its own - Turn on the sandbox with
-sortools.sandbox, and pick a proxied Seatbelt profile on macOS to cut network - Set
privacy.usageStatisticsEnabledto false to stop usage statistics - Since 0.63.0, plans run without interactive confirmation in non-interactive mode, so set the approval mode explicitly before a headless run
- 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
- Agent Zero vs boxes.dev
- Agent Zero vs Gemini CLI
- Aider vs boxes.dev
- Aider vs Gemini CLI
- Amp vs boxes.dev
- Amp vs Gemini CLI
- Antigravity CLI vs boxes.dev
- Antigravity CLI vs Gemini CLI
- Auggie CLI vs boxes.dev
- Auggie CLI vs Gemini CLI
- AXLR vs boxes.dev
- AXLR vs Gemini CLI
- boxes.dev vs Claude Code
- boxes.dev vs Click
- boxes.dev vs Cline
- boxes.dev vs Conductor
- boxes.dev vs Crush
- boxes.dev vs Cursor CLI
- boxes.dev vs DeepSeek Harness (dsh)
- boxes.dev vs dsh-superagent (DeepSeek)
- boxes.dev vs Devin
- boxes.dev vs Droid CLI
- boxes.dev vs Pi
- boxes.dev vs Emdash
- boxes.dev vs Friday
- boxes.dev vs GitHub Copilot CLI
- boxes.dev vs goose
- boxes.dev vs Harness²
- boxes.dev vs HarnessRouter
- boxes.dev vs Jules
- boxes.dev vs Junie CLI
- boxes.dev vs Kilo Code CLI
- boxes.dev vs Kimi Code CLI
- boxes.dev vs Kiro CLI
- boxes.dev vs Letta
- boxes.dev vs mini-swe-agent
- boxes.dev vs MiniMax Code
- boxes.dev vs Mistral Vibe CLI
- boxes.dev vs Muse Code
- boxes.dev vs OpenAI Agents API
- boxes.dev vs OpenAI Codex
- boxes.dev vs OpenCode
- boxes.dev vs OpenHands
- boxes.dev vs OpenMausBot
- boxes.dev vs Orca
- boxes.dev vs Paseo
- boxes.dev vs Prime Agent
- boxes.dev vs Qoder CLI
- boxes.dev vs Qwen Code
- boxes.dev vs Mirror CLI
- boxes.dev vs Rovo Dev CLI
- boxes.dev vs Sculptor
- boxes.dev vs T3 Code
- boxes.dev vs Traycer
- boxes.dev vs Unstoppable
- boxes.dev vs Verdent
- boxes.dev vs Vibe-Trading
- boxes.dev vs Warp (Warp Agent CLI and the Oz Agent API)
- Claude Code vs Gemini CLI
- Click vs Gemini CLI
- Cline vs Gemini CLI
- Conductor vs Gemini CLI
- Crush vs Gemini CLI
- Cursor CLI vs Gemini CLI
- DeepSeek Harness (dsh) vs Gemini CLI
- dsh-superagent (DeepSeek) vs Gemini CLI
- Devin vs Gemini CLI
- Droid CLI vs Gemini CLI
- Pi vs Gemini CLI
- Emdash vs Gemini CLI
- Gemini CLI vs GitHub Copilot CLI
- Gemini CLI vs goose
- Gemini CLI vs Harness²
- Gemini CLI vs HarnessRouter
- Gemini CLI vs Jules
- Gemini CLI vs Junie CLI
- Gemini CLI vs Kilo Code CLI
- Gemini CLI vs Kimi Code CLI
- Gemini CLI vs Kiro CLI
- Gemini CLI vs Letta
- Gemini CLI vs mini-swe-agent
- Gemini CLI vs MiniMax Code
- Gemini CLI vs Mistral Vibe CLI
- Gemini CLI vs Muse Code
- Gemini CLI vs OpenAI Agents API
- Gemini CLI vs OpenAI Codex
- Gemini CLI vs OpenCode
- Gemini CLI vs OpenHands
- Gemini CLI vs OpenMausBot
- Gemini CLI vs Orca
- Gemini CLI vs Paseo
- Gemini CLI vs Prime Agent
- Gemini CLI vs Qoder CLI
- Gemini CLI vs Qwen Code
- Gemini CLI vs Mirror CLI
- Gemini CLI vs Rovo Dev CLI
- Gemini CLI vs Sculptor
- Gemini CLI vs T3 Code
- Gemini CLI vs Traycer
- Gemini CLI vs Unstoppable
- Gemini CLI vs Verdent
- Gemini CLI vs Vibe-Trading
- Gemini CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs boxes.dev
- Agent Relay vs Gemini CLI
- boxes.dev vs Clawboo
- boxes.dev vs CLI Manager
- boxes.dev vs Harness
- boxes.dev vs herdr
- boxes.dev vs Paperclip
- boxes.dev vs Parallax
- Clawboo vs Gemini CLI
- CLI Manager vs Gemini CLI
- Friday vs Gemini CLI
- Gemini CLI vs Harness
- Gemini CLI vs herdr
- Gemini CLI vs Paperclip
- Gemini CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/boxes-dev-vs-gemini-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/boxes-dev.json·/api/v1/tools/gemini-cli.json - From a terminal
anchor compare boxes-dev gemini-cli(the CLI) - Over MCP
compare_tools {"a": "boxes-dev", "b": "gemini-cli"}at/mcp, no key