Head to head · Agent harnesses · October 2026 research run

boxes.dev vs Rovo Dev CLI

boxes.dev scores 53.2 (D) on agent readiness against Rovo Dev CLI's 43.3 (E), and leads in 5 of 7 scored categories. 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

  • Schema & documentation, 57 against 45
  • Agent ergonomics, 60 against 53
  • Security & auth, 69 against 48
  • Payments & pricing, 50 against 23
  • Maintenance & community, 48 against 41

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, incident history or SLA found

Rovo Dev CLI E

Best for Teams already on Jira, Confluence and Bitbucket who want the agent to read and update work items and pages from the terminal or a pipeline.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Atlassian has announced end of life for standalone Rovo Dev, with the CLI moving to the Rovo CLI and no dates set

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 boxes.dev +27

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.

Rovo Dev CLI 23

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Harness reading of the published rubric, scored on the Rovo Dev subscription the CLI needs. No payment protocol (0). Rovo Dev Standard is $20 a developer a month with 2,000 credits and extra credits are $0.01, both public. The credit multiplier for each model is shown only inside the CLI, and a task is given only as a range (5 to 50 tasks per 2,000 credits), so a run's cost can't be worked out before signing up. Judgement call between the 10 for plan-only pricing and the full 20 (15). Rovo Dev Free gives 350 credits a month, but only on Jira Standard or Premium sites, which are paid plans, and the 30-day Standard trial excludes the CLI (0). An organisation admin activates Rovo Dev and the user creates an API token in a browser (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Security & auth boxes.dev +21

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.

Rovo Dev CLI 48

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Harness reading of the framework checklist, as for the other harnesses. 30 for credentials and what leaves the machine, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The CLI processes data on the device and sends prompts to Atlassian's models, whose providers don't retain or train on them, per the Rovo privacy page and the AI Terms. The scoped token the docs create carries about 50 scopes including write, delete and admin:repository:bitbucket, the pipelines guide asks for an unscoped token, and no telemetry description for the CLI was found (12). Writes and shell commands ask by default, reads are allowed, bash rules are regex, compound commands are split and file access stays in the workspace. There is no sandbox for customers (runInSandbox is macOS only and for internal users), --yolo skips file and shell prompts, and project-level skills in a cloned repository can list pre-approved tools. We found no workspace trust step (10). MCP server instructions go into the system prompt by default, with a per-server enable_instructions switch, and the MCP page says data isn't sent to third-party tools without the user's approval (7). Administrators can turn Rovo Dev on and off per organisation and site and see credit use. Logs stay local in ~/.rovodev/logs, and no audit log of CLI actions was found (5). security.txt is valid (Expires 2027-02-04), Atlassian runs a public Bugcrowd bug bounty and publishes its fix objectives. The rollout page says Rovo Dev hasn't been externally audited for ISO 27001 or SOC 2, and we didn't check whether the bounty scope names Rovo Dev (14). 12+10+7+5+14 = 48.

Schema & documentation boxes.dev +12

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.

Rovo Dev CLI 45

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Framework reading. Server mode lists its /v3 endpoints with request bodies, and an Atlassian engineering post of 27 October 2025 says Swagger docs are served at localhost:<port>/docs. That contract is only visible on a running server, and no schema for the SSE events or the config file was published (12). No llms.txt on support.atlassian.com or developer.atlassian.com, and no Markdown twins found (0). The tools page says what allow, ask and deny do, what YOLO mode skips and that MCP tools keep their permissions, and the settings page gives each default. Little says when not to use a mode (12). Permission levels, console output formats and tool names are enumerated in the settings reference with defaults (10). Server mode has curl, Python and JavaScript examples. No exit codes or error responses are documented beyond the post's note that a failed entitlement check disables every endpoint except healthcheck and shutdown (7). The API path is versioned (/v3), but there is no public changelog for Rovo Dev builds (4). 12+0+12+10+7+4 = 45.

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

Rovo Dev CLI 53

Per the 18 October check, re-read on 5 November where named (settings, rollout, use, pricing, licensing FAQ, AI Terms and Customer Agreement pages unchanged). Framework reading, adapted to a harness driven by a pipeline. Per-tool allow, ask and deny, allowedMcpServers and disabledMcpServers, tool lists on subagents and skills, and /prune to drop tool results from context (15). The console output format is markdown, simple or raw. No JSON output for acli rovodev run is documented, server mode streams JSON events, and no turn or spend cap exists beyond the credit allowance and /efficiency (10). No exit codes are documented. Server mode reports entitlement and credit failures, per the engineering post (6). Sessions persist with --restore, fork and rename. --worktree isolates a run with a lock and keeps the worktree when a non-interactive run leaves changes, and server mode has cancel and reset (15). Sensible defaults, but no SDK, and a run needs an API token, a Rovo Dev licence and an activated site (7). 15+10+6+15+7 = 53.

Maintenance & community boxes.dev +7

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.

Rovo Dev CLI 41

Atlassian's AtlasCode extension, which downloads the same Rovo Dev binary for the IDE, pins one Rovo Dev build in each version, read from a clone of its repository on 5 November. The builds since 18 August carry a beta suffix (b1, and b3 after b1 for 202609.9.1), so they count only where a default install gets them, as azure-mcp's and deepseek-harness's pre-releases did. AtlasCode's stable 4.0.33 of 16 October 2026 ships 202610.16.1b1. The later pin, 202610.27.1b1 on 29 October, reached only its nightly pre-releases. We didn't run the CLI to read the version it installs. Judgement call (30). AtlasCode pinned ten builds between 18 August and 29 October 2026, but only 202610.16.1b1 reached a stable AtlasCode version, so one release in the 90 days from 7 August (0). No public changelog for the builds. Support is through Atlassian Support and the community, where the Rovo Dev board was last active on 16 January 2026, per the 18 October check (5). No SDK and no registry entry. The server-mode API is kept current for the IDE extension (3). The Homebrew formula in Atlassian's own tap carries checksums and the Linux repositories are signed. There's no public CI (3). 30+0+5+3+3 = 41.

Score by category

CategoryWeightboxes.devRovo Dev CLIEdge
Reliability16%3235Rovo Dev CLI +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5745boxes.dev +12
Agent ergonomics13%6053boxes.dev +7
Security & auth14%6948boxes.dev +21
Payments & pricing10%5023boxes.dev +27
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4841boxes.dev +7
Transparency & trust7%6063Rovo Dev CLI +3
Negative events≤1500
TotalD 53.2/100E 43.3/100

Facts side by side

Factboxes.devRovo Dev CLI
KindMCP serverAgent harness
VendorBoxes, Inc.Atlassian
Hosted endpointhttps://api.boxes.dev/mcpno (local only)
TransportsStreamable HTTP, HTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceProprietary. The service runs under the Common Paper Cloud Service Agreement 2.1, and the @boxes-dev/cli package is marked UNLICENSEDProprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published
Read-only variant documentednono
llms.txtyesno
Last release2026-11-172026-10-16
Terms last updated2026-10-20no date given
Privacy policy last updated2026-10-21couldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviewsnone2/5 (4)

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.

Rovo Dev CLI

Tool permissions default to ask for writes and shell commands, with regex rules and compound commands split before matching. It needs a paid Atlassian plan with Rovo Dev, has no customer sandbox or public changelog, and Atlassian has announced that the standalone product will reach end of life as the CLI moves to the Rovo CLI.

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

Rovo Dev CLI

  1. Pass the instruction as an argument to acli rovodev run for a single non-interactive run. No JSON output flag or exit codes are documented
  2. Use acli rovodev serve <port> and stream /v3/stream_chat?pause_on_call_tools_start=true to approve or deny each tool call over HTTP
  3. Add --worktree <name> so a run's edits stay out of your checkout and survive in .rovodev/worktrees/<name>
  4. Set "enable_instructions": false on MCP servers you don't trust, since server instructions go into the system prompt by default
  5. Check /usage before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on

Questions

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

boxes.dev scores 53.2 (D) on agent readiness against Rovo Dev CLI's 43.3 (E), and leads in 5 of 7 scored categories.

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

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

Other comparisons with boxes.dev or Rovo Dev 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.