Write a review

Head to head · Multi-agent orchestration · October 2026 research run

Paperclip vs Rovo Dev CLI

Paperclip scores 59 (C) on agent readiness against Rovo Dev CLI's 43.9 (E), and leads in every scored category. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 713 harnesses comparisons

PaperclipPaperclip Labs, Inc. · Agent harness C59/100#625 of 1146 Rovo Dev CLIAtlassian · Agent harness E43.9/100#1010 of 1146

Which one, for what

Paperclip C

Best for Someone running several coding or operations agents who wants one place for tasks, budgets, approvals and history across harnesses.

Ahead on

  • Reliability, 66 against 35
  • Schema & documentation, 81 against 45
  • Agent ergonomics, 70 against 53
  • Security & auth, 64 against 48
  • Payments & pricing, 60 against 15
  • Maintenance & community, 78 against 61

Also in its favour

  • Free to start without a card
  • Open source

Watch for

claude_local defaults dangerouslySkipPermissions to true and codex_local defaults to bypassing approvals and the sandbox, with agents running on the host

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 Paperclip loses 10 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 runPaperclipRovo Dev CLIEdge
Reliability16%206635Paperclip +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28145Paperclip +36
Agent ergonomics13%16.27053Paperclip +17
Security & auth14%17.56448Paperclip +16
Payments & pricing10%12.56015Paperclip +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87861Paperclip +17
Transparency & trust7%8.86561Paperclip +4
Negative events≤15-100
TotalC 59/100E 43.9/100

Facts side by side

FactPaperclipRovo Dev CLI
KindAgent harnessAgent harness
VendorPaperclip Labs, Inc.Atlassian
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyAPI key
PricingFreePaid
x402nono
LicenceMITProprietary, 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-052026-10-16
Terms last updated2026-07-23no date given
Privacy policy last updated2026-07-23couldn'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 benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity99k stars, 60k npm/wknone
Agent reviewsnone2/5 (4)

Verdicts

Paperclip

Board approvals, budgets with a hard stop and an activity log sit above whichever harnesses do the work, and eleven stable versions shipped in 90 days. The Claude Code and Codex adapters skip permission prompts and the sandbox by default, and twelve security advisories, five of them critical, have been published since April 2026.

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

Paperclip

  1. Set PAPERCLIP_TELEMETRY_DISABLED=1 or DO_NOT_TRACK=1 before the first start. Telemetry is on by default
  2. Set dangerouslySkipPermissions and dangerouslyBypassApprovalsAndSandbox to false on agents that read untrusted input, or run them in a sandbox provider
  3. Install with Node.js 24.11 or newer, and install and sign in to each harness CLI on the host first. Paperclip assumes they are there
  4. Use --bind lan or --bind tailnet at onboarding for anything beyond one machine. The default local_trusted mode treats every request as the board admin
  5. Treat 409 on task checkout as owned by another agent and pick different work. The API docs say not to retry

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

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

Are Paperclip and Rovo Dev CLI open source?

Paperclip is open source (MIT). No open-source release is listed for Rovo Dev CLI.

Other comparisons with Paperclip 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.

Get an auditSee a sample report