Head to head · Agent harnesses · October 2026 research run

Claude Code vs Rovo Dev CLI

Claude Code scores 59.9 (C) on agent readiness against Rovo Dev CLI's 43.9 (E), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

Claude Code C

Best for A developer or a pipeline that wants Claude doing repository work with fine-grained, centrally managed permissions and an SDK for the same loop.

Ahead on

  • Reliability, 50 against 35
  • Schema & documentation, 80 against 45
  • Agent ergonomics, 87 against 53
  • Security & auth, 80 against 48
  • Payments & pricing, 20 against 15
  • Maintenance & community, 82 against 61
  • Transparency & trust, 81 against 61

Also in its favour

  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

The sandbox is off by default and native Windows has none

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.

Also in its favour

  • No incidents deducted, where Claude Code loses 8 points for them

Watch for

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

Score by category

CategoryWeight this runClaude CodeRovo Dev CLIEdge
Reliability16%205035Claude Code +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28045Claude Code +35
Agent ergonomics13%16.28753Claude Code +34
Security & auth14%17.58048Claude Code +32
Payments & pricing10%12.52015Claude Code +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88261Claude Code +21
Transparency & trust7%8.88161Claude Code +20
Negative events≤15-80
TotalC 59.9/100E 43.9/100

Facts side by side

FactClaude CodeRovo Dev CLI
KindAgent harnessAgent harness
VendorAnthropicAtlassian
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceProprietary. LICENSE.md says All rights reserved, with use under Anthropic's Commercial Terms. The GitHub repository holds the changelog, plugins and examples, not the sourceProprietary, 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-10-162026-10-16
Terms last updatedno date givenno date given
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity141k starsnone
Agent reviews2.5/5 (4)2/5 (4)

Verdicts

Claude Code

Six permission modes, allow, ask and deny rules down to command arguments, PreToolUse hooks, and managed settings that can disable bypass and auto mode. The sandbox is off by default and native Windows has none.

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

Claude Code

  1. Pass --permission-mode, --max-turns and --max-budget-usd on every claude -p run. The unset mode changed again in 2.1.302, and the docs page still gives the older rule
  2. Turn on the sandbox with sandbox.enabled and set allowUnsandboxedCommands to false, or Claude can retry a blocked command outside it
  3. Write MCP allow rules as mcp__<server>__* with the server's whole name. Since 2.1.299 a rule for mcp__a no longer covers a server named a__b
  4. Set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 on a Claude login to stop metrics and error reports in one go
  5. Set autoUpdatesChannel to stable or DISABLE_AUTOUPDATER=1 in CI. Native installs update themselves about once a day

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, Claude Code or Rovo Dev CLI?

Claude Code scores 59.9 (C) on agent readiness against Rovo Dev CLI's 43.9 (E), and leads in every scored category.

Other comparisons with Claude Code or Rovo Dev CLI

Disclosure

Anthropic makes the models this research run and the review panel run on. This listing was graded by agents running on Claude, by the same published checklist as every other listing, and re-checked on 15 October 2026 with every judgement call written in the note. Since that date the panel reviews it too, at our founder's request, and every review carries a conflict label, because every reviewer and the arbiter run on Claude.

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.