{ "data": { "a": { "slug": "rovo-dev-cli", "name": "Rovo Dev CLI", "vendor": "Atlassian", "vendorUrl": "https://support.atlassian.com/rovo/docs/use-rovo-dev-cli/", "kind": "harness", "category": "agent-harnesses", "summary": "Atlassian's terminal coding agent, run as `acli rovodev` in the Atlassian CLI with Jira, Confluence and Bitbucket context, one-shot instructions and a local HTTP server mode. Atlassian has announced it will become the Atlassian Rovo CLI.", "url": "https://www.anchorterminal.com/tools/rovo-dev-cli", "markdownUrl": "https://www.anchorterminal.com/tools/rovo-dev-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rovo-dev-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rovo-dev-cli.json", "dns": "rovo-dev-cli.grade.anchorterminal.com", "license": "Proprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published", "transports": [], "packages": [], "auth": "api-key", "authNotes": "`acli rovodev auth login` with an Atlassian account email and an API token. The docs link creates a scoped token for Rovo Dev with about 50 scopes across Jira, Confluence, Bitbucket, Compass and Goals, including write, delete and admin:repository:bitbucket, and the user sets its expiry. The Bitbucket agentic pipelines guide asks for an unscoped API token in `USER_API_TOKEN` with `USER_EMAIL`. The site must have Rovo Dev activated by an organisation admin and the user needs a Rovo Dev credit allowance.", "pricing": "paid", "pricingNotes": "Rovo Dev Standard is $20 a developer a month with 2,000 Rovo Dev credits, and extra usage is $0.01 a credit if the organisation turns it on. Rovo Dev Free gives 350 credits a user a month on Jira Standard or Premium sites, which are paid Jira plans. The 30-day Standard trial excludes the CLI. Models carry credit multipliers shown only inside the CLI with `/models` (checked 2026-10-18).", "priceSummary": "$20 / seat-mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Rovo Dev docs, the pricing page or the licensing FAQ (checked 2026-10-18).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-18" }, "docsUrl": "https://support.atlassian.com/rovo/docs/use-rovo-dev-cli/", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "official", "harness", "coding-agent", "cli", "closed-source", "mcp", "paid", "no-status-page" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 44.1, "grade": "E", "agentReady": false, "rank": 1217, "ranked": true, "rankOf": 1486, "categoryRank": 49, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 61, "payments": 15, "reliability": 35, "schema": 45, "security": 48, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-18" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Writes, deletes and shell commands ask by default, reads are allowed, and compound commands are split and checked one by one", "A local server mode exposes chat, tool approval, sessions and direct tool calls over HTTP with server-sent events", "`--worktree` runs each task in its own Git worktree with a lock, and keeps it when a non-interactive run leaves changes", "Built-in Atlassian MCP server for Jira, Confluence and Bitbucket context, plus stdio, HTTP and SSE MCP clients", "Plan price and the $0.01 extra credit price are public, and an organisation can cap extra usage" ], "weaknesses": [ "Atlassian has announced end of life for standalone Rovo Dev, with the CLI moving to the Rovo CLI and no dates set", "No sandbox for customers. The documented bash sandbox is macOS only and limited to internal users", "No public changelog for Rovo Dev builds, and the Atlassian CLI changelog stops at v1.3.15 while its package repository serves 1.3.39", "Requires a paid Jira or Rovo Dev plan, the Standard trial excludes the CLI, and an admin must activate it", "The rollout page says Rovo Dev hasn't been externally audited for ISO 27001 or SOC 2 and doesn't support data residency" ], "agentNotes": [ "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", "Use `acli rovodev serve \u003cport\u003e` and stream `/v3/stream_chat?pause_on_call_tools_start=true` to approve or deny each tool call over HTTP", "Add `--worktree \u003cname\u003e` so a run's edits stay out of your checkout and survive in `.rovodev/worktrees/\u003cname\u003e`", "Set `\"enable_instructions\": false` on MCP servers you don't trust, since server instructions go into the system prompt by default", "Check `/usage` before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.1 } ], "editorialScores": { "ergonomics": 53, "maintenance": 61, "payments": 15, "reliability": 35, "schema": 45, "security": 48, "transparency": 41 }, "provenanceScore": 84, "checked": { "categories": { "ergonomics": "2026-10-18", "maintenance": "2026-10-18", "payments": "2026-10-18", "reliability": "2026-10-18", "schema": "2026-10-18", "security": "2026-10-18", "transparency": "2026-10-18" }, "last": "2026-10-18", "lastMoved": "2026-10-27", "oldest": "2026-10-18", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew tap atlassian/homebrew-acli \u0026\u0026 brew install acli \u0026\u0026 acli rovodev auth login", "headless": { "curl": "curl -X POST http://localhost:8123/v3/set_chat_message -H \"Content-Type: application/json\" -d '{\"message\": \"Run the tests and show me any failures\"}'", "run": "acli rovodev run --worktree fix-tests \"Fix the failing test in tests/test_api.py\"", "server": "acli rovodev serve 8123" } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/rovo-dev-cli" }, "sameCompany": [ "atlassian-rovo-mcp" ], "area": "frameworks", "unitPrices": [ { "item": "Rovo Dev Standard", "unit": "seat-month", "usd": 20, "note": "per developer, with 2,000 Rovo Dev credits" }, { "item": "Extra Rovo Dev credit", "unit": "credit", "usd": 0.01, "note": "Standard, when extra usage is turned on for the organisation" } ], "provenance": { "legalEntity": "Atlassian Pty Ltd", "domain": "atlassian.com", "domainRegistered": "2001-03-19", "endpointOnVendorDomain": null, "terms": "https://www.atlassian.com/legal/atlassian-customer-agreement", "privacy": "https://www.atlassian.com/legal/privacy-policy", "statusPage": "", "changelog": "https://developer.atlassian.com/cloud/acli/changelog/", "securityTxt": "valid", "checked": "2026-10-18", "notes": [ "The product-specific terms name Atlassian Pty Ltd for AI Offerings, which carry the AI Terms (effective 17 August 2026).", "The domain registration date is from the atlassian-rovo-mcp listing and wasn't re-read on 18 October.", "rovo.status.atlassian.com lists Rovo components (Chat, Agents, MCP, Studio and others) with no Rovo Dev component, so the CLI's hosted dependency has no status component.", "The Atlassian CLI changelog's newest release entry is v1.3.15-stable of 25 March 2026, while the apt repository served 1.3.39-stable on 23 September 2026. No changelog for Rovo Dev builds was found outside the CLI's own `/changelog` command.", "www.atlassian.com/.well-known/security.txt is PGP-signed with Expires 2027-02-04." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rovo-dev-cli.json", "live": { "slug": "rovo-dev-cli", "securityTxt": { "url": "https://atlassian.com/.well-known/security.txt", "state": "valid", "expires": "2027-02-04T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:05.264223293Z" }, "domain": { "domain": "atlassian.com", "registered": "2001-03-19", "source": "https://rdap.verisign.com/com/v1/domain/atlassian.com", "checkedAt": "2026-11-01T14:11:11.424415394Z" }, "pages": [ { "url": "https://developer.atlassian.com/cloud/acli/changelog/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:02:52.455010303Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3f576acf37cb" }, { "url": "https://www.atlassian.com/licensing/rovo-dev", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:25:06.194504971Z", "changedAt": "2026-11-06T13:46:20.975925576Z", "fingerprint": "3d42ff98b18e" }, { "url": "https://www.atlassian.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:25:04.16666345Z", "changedAt": "2026-11-03T08:03:10.921862458Z", "fingerprint": "caa9a812c573" }, { "url": "https://www.atlassian.com/legal/atlassian-customer-agreement", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:25:01.042991876Z", "changedAt": "2026-11-04T08:37:16.952761534Z", "fingerprint": "e926b026c3ca" } ], "updatedAt": "2026-11-07T16:00:05.264223293Z" } }, "answer": "Rovo Dev CLI scores 44.1 (E) on agent readiness against Verdent's 39.7 (E), and leads in 3 of 7 scored categories. Verdent leads on reliability, schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "verdent", "name": "Verdent", "vendor": "Verdent AI, Inc.", "vendorUrl": "https://www.verdent.ai", "kind": "harness", "category": "agent-harnesses", "summary": "Verdent is a coding agent from Verdent AI, Inc., with a desktop app for macOS and Windows, VS Code and JetBrains extensions and a browser edition. It plans tasks, runs parallel workers in git worktrees and uses MCP servers.", "url": "https://www.anchorterminal.com/tools/verdent", "markdownUrl": "https://www.anchorterminal.com/tools/verdent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/verdent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/verdent.json", "dns": "verdent.grade.anchorterminal.com", "license": "Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published", "transports": [], "packages": [], "auth": "mixed", "authNotes": "A person signs in to a Verdent account with Google, GitHub or email in a browser. Model use runs on Verdent credits through llm-proxy.verdent.ai, or on the user's own Anthropic, OpenAI or OpenRouter key (BYOK). BYOA runs workers on a local Claude Code or Codex CLI with keys kept on the machine. No API key or token for driving Verdent from another program was found.", "pricing": "paid", "pricingNotes": "From $5 a month (Lite), then $19 Starter, $59 Pro and $179 Max with 320, 1,000 and 3,000 credits a month (doubled by a limited-time bonus). One credit is about $0.059 at provider rates. Top-ups $20 for 340 credits to $200 for 3,400. Free Mode and the free trial ended with v2.18.0 on 29 October 2026.", "priceSummary": "$5 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing page, terms or changelog (checked 2026-11-06). Subscriptions and top-ups go through Stripe.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.verdent.ai/docs/verdent-manager/getting-started/overview", "capabilities": [ "agent.harness", "agent.multi-agent", "agent.mcp-client" ], "tags": [ "official", "harness", "coding-agent", "closed-source", "desktop", "vscode", "jetbrains", "mcp", "byok", "paid-plans", "no-sandbox" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 39.7, "grade": "E", "agentReady": false, "rank": 1317, "ranked": true, "rankOf": 1486, "categoryRank": 53, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 35, "maintenance": 61, "payments": 20, "reliability": 43, "schema": 55, "security": 33, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": -2, "negativeNotes": [ "2026-11-06. The changelog says v2.18.0 of 29 October 2026 retired Free Mode, the free trial and the 100 welcome credits, while the pricing page FAQ read on 6 November still says \"Your free trial includes 100 credits\" and the 1.0 docs overview still lists a free trial. A stale claim on the vendor's own pricing page, 2 points. https://www.verdent.ai/pricing, https://www.verdent.ai/changelog" ], "verdict": "A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.", "bestFor": "A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.", "strengths": [ "Plan Mode is read-only and writes a plan.md for review before Agent Mode makes changes", "Parallel workers each run in their own git worktree, with a review column before work is accepted", "BYOA runs workers on a local Claude Code or Codex CLI, and BYOK takes Anthropic, OpenAI or OpenRouter keys", "Plan, top-up and per-credit prices are public, charged at provider token rates with no markup per the pricing page", "Every current docs page has a Markdown twin, and the changelog is dated by version" ], "weaknesses": [ "No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot", "No sandbox or network restriction documented, and the actions that need approval aren't listed", "Free Mode and the free trial ended on 29 October 2026, while the pricing page FAQ still promises 100 trial credits", "Event logging to log.verdent.ai has no documented opt-out, and the privacy policy gives no retention periods", "SOC 2 and ISO/IEC 42001 are being pursued, not held, and there is no bug bounty or security.txt" ], "agentNotes": [ "Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode", "Start large changes in Plan Mode and review plan.md before switching to Agent Mode", "Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape", "Keep work under git, since rollback relies on git and there is no sandbox", "Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 39.7 } ], "editorialScores": { "ergonomics": 35, "maintenance": 61, "payments": 20, "reliability": 43, "schema": 55, "security": 33, "transparency": 47 }, "provenanceScore": 62, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "config": { "mcpServers": { "github": { "args": [ "-y", "@modelcontextprotocol/server-github" ], "command": "npx", "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/verdent" }, "area": "frameworks", "unitPrices": [ { "item": "Lite plan", "unit": "month", "usd": 5, "note": "Eco Mode models and light usage" }, { "item": "Starter plan", "unit": "month", "usd": 19, "note": "320 credits a month, 480 with the limited-time bonus" }, { "item": "Pro plan", "unit": "month", "usd": 59, "note": "1,000 credits a month, 1,500 with the bonus" }, { "item": "Max plan", "unit": "month", "usd": 179, "note": "3,000 credits a month, 4,500 with the bonus" }, { "item": "Credit", "unit": "credit", "usd": 0.059, "note": "About $0.059, charged at provider token prices with no markup per the pricing page" } ], "provenance": { "legalEntity": "Verdent AI, Inc.", "domain": "verdent.ai", "domainRegistered": "2025-05-06", "endpointOnVendorDomain": true, "terms": "https://www.verdent.ai/terms", "privacy": "https://www.verdent.ai/privacy", "statusPage": "", "changelog": "https://www.verdent.ai/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The privacy policy names Verdent AI, Inc. as data controller, and the terms choose California law.", "The terms forbid users to crawl, scrape or otherwise harvest data or information from the Services. Public pages were read once each.", "www.verdent.ai/robots.txt allows all crawlers.", "RDAP gives verdent.ai a registration date of 6 May 2025.", "/.well-known/security.txt returns 404, and status.verdent.ai did not answer. No status page found.", "The security page says SOC 2 and ISO/IEC 42001 are being pursued, not held, and takes vulnerability reports at hi@verdent.ai with acknowledgement within five business days." ], "score": 62 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/verdent.json", "live": { "slug": "verdent", "securityTxt": { "url": "https://verdent.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:33.272105482Z" }, "pages": [ { "url": "https://www.verdent.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:36:28.662063151Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bac05e4e426e" }, { "url": "https://www.verdent.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:36:31.354667853Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3ec1d3c07d70" }, { "url": "https://www.verdent.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:36:33.295376926Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "206b6ec23a6a" } ], "updatedAt": "2026-11-07T15:59:33.272105482Z" } }, "edges": [ { "by": 18, "category": "ergonomics", "leads": "rovo-dev-cli", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35." }, "scores": { "a": 53, "b": 35 } }, { "by": 15, "category": "security", "leads": "rovo-dev-cli", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33." }, "scores": { "a": 48, "b": 33 } }, { "by": 10, "category": "schema", "leads": "verdent", "name": "Schema \u0026 documentation", "reasons": { "a": "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:\u003cport\u003e/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.", "b": "Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as \"certain tool executions\" and \"destructive operations\" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55." }, "scores": { "a": 45, "b": 55 } }, { "by": 8, "category": "reliability", "leads": "verdent", "name": "Reliability", "reasons": { "a": "Local-package reading, the same as the other closed-source harnesses. Rovo Dev ships inside the Atlassian CLI, which installs from a Homebrew tap with SHA-256 checksums, signed apt and yum repositories and curl downloads for macOS, Linux and Windows on amd64 and arm64, and Rovo Dev downloads itself on first use (20). No public CI or test suite, since the source isn't published (0). No public issue tracker. The Rovo Dev community board was last active on 16 January 2026, and bugs otherwise go to `/feedback` and Atlassian Support, so open crash reports can't be counted (8). Rovo Dev builds moved from 0.13.x to date-based versions such as 202604.30.2 and 202610.16.1b1, per AtlasCode's changelog and manifest, and have no public changelog, and the Atlassian CLI changelog stops at v1.3.15 while its repository serves 1.3.39 (2). Rovo Dev has been rolling out as a product since October 2025, but the version number carries no stability signal and Atlassian has announced that the standalone product will reach end of life. Judgement call (5). The CLI runs against Atlassian's hosted service, and the Rovo status page has no Rovo Dev component. 20+0+8+2+5 = 35.", "b": "Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43." }, "scores": { "a": 35, "b": 43 } }, { "by": 8, "category": "transparency", "leads": "rovo-dev-cli", "name": "Transparency \u0026 trust", "reasons": { "a": "Proprietary, with clear terms. The Atlassian Customer Agreement (effective 1 October 2026) and the AI Terms (effective 17 August 2026), which say Input and Output are Customer Data and that subcontractors may not train on them (15). The Rovo privacy page keeps Chat and agent inputs and outputs for 30 days and says Rovo has SOC 2, ISO 27001 and data residency, while the Rovo Dev rollout page (modified 27 August 2026) says Rovo Dev has none of the three. We found no retention period for Rovo Dev sessions sent to Atlassian (12). The licensing FAQ promises at least 60 days' notice before Rovo Dev's end of life and dates the Code Reviewer move to 3 December 2026, but gives no date for the CLI's move to the Rovo CLI. Each Atlassian CLI version is supported for six months (14). No telemetry description or opt-out for the CLI was found. AtlasCode's changelog documents Rovo Dev telemetry events in the IDE, which this listing doesn't cover (0). 15+12+14+0 = 41.", "b": "Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47." }, "scores": { "a": 63, "b": 55 } }, { "by": 5, "category": "payments", "leads": "verdent", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20." }, "scores": { "a": 15, "b": 20 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Atlassian", "b": "Verdent AI, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published", "b": "Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-16", "b": "2026-10-29", "name": "Last release" }, { "a": "no date given", "b": "2026-05-25", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-05-26", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "2/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Rovo Dev CLI scores 44.1 (E) on agent readiness against Verdent's 39.7 (E), and leads in 3 of 7 scored categories. Verdent leads on reliability, schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, Rovo Dev CLI or Verdent?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 53 against 35", "Security \u0026 auth, 48 against 33", "Transparency \u0026 trust, 63 against 55" ], "also": null, "goodFor": "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.", "slug": "rovo-dev-cli", "watchFor": "Atlassian has announced end of life for standalone Rovo Dev, with the CLI moving to the Rovo CLI and no dates set" }, { "aheadOn": [ "Reliability, 43 against 35", "Schema \u0026 documentation, 55 against 45", "Payments \u0026 pricing, 20 against 15" ], "also": null, "goodFor": "A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.", "slug": "verdent", "watchFor": "No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot" } ], "history": { "rovo-dev-cli": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 43.9, "fromGrade": "E", "to": 44.1, "toGrade": "E" } ], "verdent": null }, "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-rovo-dev-cli.json", "title": "Agent Zero vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-verdent.json", "title": "Agent Zero vs Verdent", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-rovo-dev-cli.json", "title": "Aider vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/aider-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-verdent.json", "title": "Aider vs Verdent", "url": "https://www.anchorterminal.com/compare/aider-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-rovo-dev-cli.json", "title": "Amp vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/amp-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-verdent.json", "title": "Amp vs Verdent", "url": "https://www.anchorterminal.com/compare/amp-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-rovo-dev-cli.json", "title": "Antigravity CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent.json", "title": "Antigravity CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-rovo-dev-cli.json", "title": "Auggie CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/auggie-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-verdent.json", "title": "Auggie CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/auggie-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/axlr-vs-rovo-dev-cli.json", "title": "AXLR vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/axlr-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/axlr-vs-verdent.json", "title": "AXLR vs Verdent", "url": "https://www.anchorterminal.com/compare/axlr-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-rovo-dev-cli.json", "title": "Claude Code vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/claude-code-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-verdent.json", "title": "Claude Code vs Verdent", "url": "https://www.anchorterminal.com/compare/claude-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-rovo-dev-cli.json", "title": "Cline vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-verdent.json", "title": "Cline vs Verdent", "url": "https://www.anchorterminal.com/compare/cline-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/conductor-vs-rovo-dev-cli.json", "title": "Conductor vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/conductor-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/conductor-vs-verdent.json", "title": "Conductor vs Verdent", "url": "https://www.anchorterminal.com/compare/conductor-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.json", "title": "Crush vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-verdent.json", "title": "Crush vs Verdent", "url": "https://www.anchorterminal.com/compare/crush-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-rovo-dev-cli.json", "title": "Cursor CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.json", "title": "Cursor CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-rovo-dev-cli.json", "title": "DeepSeek Harness (dsh) vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent.json", "title": "DeepSeek Harness (dsh) vs Verdent", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli.json", "title": "dsh-superagent (DeepSeek) vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent.json", "title": "dsh-superagent (DeepSeek) vs Verdent", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-rovo-dev-cli.json", "title": "Devin vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/devin-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-verdent.json", "title": "Devin vs Verdent", "url": "https://www.anchorterminal.com/compare/devin-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-rovo-dev-cli.json", "title": "Droid CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-verdent.json", "title": "Droid CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-rovo-dev-cli.json", "title": "Pi vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-verdent.json", "title": "Pi vs Verdent", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli.json", "title": "Emdash vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-verdent.json", "title": "Emdash vs Verdent", "url": "https://www.anchorterminal.com/compare/emdash-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-rovo-dev-cli.json", "title": "Gemini CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-verdent.json", "title": "Gemini CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-rovo-dev-cli.json", "title": "GitHub Copilot CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent.json", "title": "GitHub Copilot CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-rovo-dev-cli.json", "title": "goose vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/goose-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-verdent.json", "title": "goose vs Verdent", "url": "https://www.anchorterminal.com/compare/goose-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-rovo-dev-cli.json", "title": "Harness² vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/harness2-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-verdent.json", "title": "Harness² vs Verdent", "url": "https://www.anchorterminal.com/compare/harness2-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli.json", "title": "HarnessRouter vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.json", "title": "HarnessRouter vs Verdent", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-rovo-dev-cli.json", "title": "Jules vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/jules-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-verdent.json", "title": "Jules vs Verdent", "url": "https://www.anchorterminal.com/compare/jules-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-rovo-dev-cli.json", "title": "Junie CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/junie-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-verdent.json", "title": "Junie CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/junie-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli.json", "title": "Kilo Code CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent.json", "title": "Kilo Code CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli.json", "title": "Kimi Code CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent.json", "title": "Kimi Code CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.json", "title": "Kiro CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.json", "title": "Kiro CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/letta-vs-rovo-dev-cli.json", "title": "Letta vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/letta-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/letta-vs-verdent.json", "title": "Letta vs Verdent", "url": "https://www.anchorterminal.com/compare/letta-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-rovo-dev-cli.json", "title": "mini-swe-agent vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent.json", "title": "mini-swe-agent vs Verdent", "url": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/minimax-code-vs-rovo-dev-cli.json", "title": "MiniMax Code vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/minimax-code-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/minimax-code-vs-verdent.json", "title": "MiniMax Code vs Verdent", "url": "https://www.anchorterminal.com/compare/minimax-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-rovo-dev-cli.json", "title": "Mistral Vibe CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent.json", "title": "Mistral Vibe CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/muse-code-vs-rovo-dev-cli.json", "title": "Muse Code vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/muse-code-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/muse-code-vs-verdent.json", "title": "Muse Code vs Verdent", "url": "https://www.anchorterminal.com/compare/muse-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli.json", "title": "OpenAI Agents API vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent.json", "title": "OpenAI Agents API vs Verdent", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openai-codex-vs-rovo-dev-cli.json", "title": "OpenAI Codex vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/openai-codex-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/openai-codex-vs-verdent.json", "title": "OpenAI Codex vs Verdent", "url": "https://www.anchorterminal.com/compare/openai-codex-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/opencode-vs-rovo-dev-cli.json", "title": "OpenCode vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/opencode-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/opencode-vs-verdent.json", "title": "OpenCode vs Verdent", "url": "https://www.anchorterminal.com/compare/opencode-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openhands-vs-rovo-dev-cli.json", "title": "OpenHands vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/openhands-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/openhands-vs-verdent.json", "title": "OpenHands vs Verdent", "url": "https://www.anchorterminal.com/compare/openhands-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/orca-vs-rovo-dev-cli.json", "title": "Orca vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/orca-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/orca-vs-verdent.json", "title": "Orca vs Verdent", "url": "https://www.anchorterminal.com/compare/orca-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli.json", "title": "Paseo vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/paseo-vs-verdent.json", "title": "Paseo vs Verdent", "url": "https://www.anchorterminal.com/compare/paseo-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/prime-agent-vs-rovo-dev-cli.json", "title": "Prime Agent vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/prime-agent-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/prime-agent-vs-verdent.json", "title": "Prime Agent vs Verdent", "url": "https://www.anchorterminal.com/compare/prime-agent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/qoder-cli-vs-rovo-dev-cli.json", "title": "Qoder CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/qoder-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.json", "title": "Qoder CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/qoder-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/qwen-code-vs-rovo-dev-cli.json", "title": "Qwen Code vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/qwen-code-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/qwen-code-vs-verdent.json", "title": "Qwen Code vs Verdent", "url": "https://www.anchorterminal.com/compare/qwen-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/reflection-mirror-vs-rovo-dev-cli.json", "title": "Mirror CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/reflection-mirror-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.json", "title": "Mirror CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-sculptor.json", "title": "Rovo Dev CLI vs Sculptor", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-sculptor" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code.json", "title": "Rovo Dev CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-traycer.json", "title": "Rovo Dev CLI vs Traycer", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-traycer" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-unstoppable.json", "title": "Rovo Dev CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-vibe-trading.json", "title": "Rovo Dev CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-warp.json", "title": "Rovo Dev CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/sculptor-vs-verdent.json", "title": "Sculptor vs Verdent", "url": "https://www.anchorterminal.com/compare/sculptor-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-verdent.json", "title": "T3 Code vs Verdent", "url": "https://www.anchorterminal.com/compare/t3-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/traycer-vs-verdent.json", "title": "Traycer vs Verdent", "url": "https://www.anchorterminal.com/compare/traycer-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/verdent-vs-vibe-trading.json", "title": "Verdent vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/verdent-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/verdent-vs-warp.json", "title": "Verdent vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/verdent-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.json", "title": "Clawboo vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-verdent.json", "title": "Clawboo vs Verdent", "url": "https://www.anchorterminal.com/compare/clawboo-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-rovo-dev-cli.json", "title": "CLI Manager vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-verdent.json", "title": "CLI Manager vs Verdent", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-rovo-dev-cli.json", "title": "Harness vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent.json", "title": "Harness vs Verdent", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openmausbot-vs-rovo-dev-cli.json", "title": "OpenMausBot vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/openmausbot-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/openmausbot-vs-verdent.json", "title": "OpenMausBot vs Verdent", "url": "https://www.anchorterminal.com/compare/openmausbot-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/paperclip-vs-rovo-dev-cli.json", "title": "Paperclip vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/paperclip-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/paperclip-vs-verdent.json", "title": "Paperclip vs Verdent", "url": "https://www.anchorterminal.com/compare/paperclip-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/parallax-agents-vs-rovo-dev-cli.json", "title": "Parallax vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/parallax-agents-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/parallax-agents-vs-verdent.json", "title": "Parallax vs Verdent", "url": "https://www.anchorterminal.com/compare/parallax-agents-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/unstoppable-vs-verdent.json", "title": "Unstoppable vs Verdent", "url": "https://www.anchorterminal.com/compare/unstoppable-vs-verdent" } ], "panel": null, "scores": [ { "by": 8, "edge": "verdent", "key": "reliability", "name": "Reliability", "rovo-dev-cli": 35, "verdent": 43, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "verdent", "key": "schema", "name": "Schema \u0026 documentation", "rovo-dev-cli": 45, "verdent": 55, "weight": 13 }, { "by": 18, "edge": "rovo-dev-cli", "key": "ergonomics", "name": "Agent ergonomics", "rovo-dev-cli": 53, "verdent": 35, "weight": 13 }, { "by": 15, "edge": "rovo-dev-cli", "key": "security", "name": "Security \u0026 auth", "rovo-dev-cli": 48, "verdent": 33, "weight": 14 }, { "by": 5, "edge": "verdent", "key": "payments", "name": "Payments \u0026 pricing", "rovo-dev-cli": 15, "verdent": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "key": "maintenance", "name": "Maintenance \u0026 community", "rovo-dev-cli": 61, "verdent": 61, "weight": 7 }, { "by": 8, "edge": "rovo-dev-cli", "key": "transparency", "name": "Transparency \u0026 trust", "rovo-dev-cli": 63, "verdent": 55, "weight": 7 } ], "summary": "Rovo Dev CLI scores 44.1 (E) on agent readiness against Verdent's 39.7 (E), and leads in 3 of 7 scored categories. Verdent leads on reliability, schema \u0026 documentation and payments \u0026 pricing. Both do agent harnesses.", "tasks": null, "tutorials": [], "verdicts": { "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.", "verdent": "A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent", "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.min.md" }, "markdown": "Rovo Dev CLI scores 44.1 (E) on agent readiness against Verdent's 39.7 (E), and leads in 3 of 7 scored categories. Verdent leads on reliability, schema \u0026 documentation and payments \u0026 pricing. Both do agent harnesses.\n\n- Rovo Dev CLI: grade E, 44.1/100, rank #1217 of 1486. Markdown https://www.anchorterminal.com/tools/rovo-dev-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/rovo-dev-cli.json\n- Verdent: grade E, 39.7/100, rank #1317 of 1486. Markdown https://www.anchorterminal.com/tools/verdent.md · JSON https://www.anchorterminal.com/api/v1/tools/verdent.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 1500 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Rovo Dev CLI (E)\n\nGood 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.\n\nAhead on:\n- Agent ergonomics, 53 against 35\n- Security \u0026 auth, 48 against 33\n- Transparency \u0026 trust, 63 against 55\n\nWatch for: Atlassian has announced end of life for standalone Rovo Dev, with the CLI moving to the Rovo CLI and no dates set\n\n### Verdent (E)\n\nGood for: A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.\n\nAhead on:\n- Reliability, 43 against 35\n- Schema \u0026 documentation, 55 against 45\n- Payments \u0026 pricing, 20 against 15\n\nWatch for: No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot\n\n\n## Why the edge\n\n### Agent ergonomics: Rovo Dev CLI +18\n\n- Rovo Dev CLI (53): 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.\n- Verdent (35): Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.\n\n### Security \u0026 auth: Rovo Dev CLI +15\n\n- Rovo Dev CLI (48): 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.\n- Verdent (33): Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.\n\n### Schema \u0026 documentation: Verdent +10\n\n- Rovo Dev CLI (45): 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:\u003cport\u003e/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.\n- Verdent (55): Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as \"certain tool executions\" and \"destructive operations\" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.\n\n### Reliability: Verdent +8\n\n- Rovo Dev CLI (35): Local-package reading, the same as the other closed-source harnesses. Rovo Dev ships inside the Atlassian CLI, which installs from a Homebrew tap with SHA-256 checksums, signed apt and yum repositories and curl downloads for macOS, Linux and Windows on amd64 and arm64, and Rovo Dev downloads itself on first use (20). No public CI or test suite, since the source isn't published (0). No public issue tracker. The Rovo Dev community board was last active on 16 January 2026, and bugs otherwise go to `/feedback` and Atlassian Support, so open crash reports can't be counted (8). Rovo Dev builds moved from 0.13.x to date-based versions such as 202604.30.2 and 202610.16.1b1, per AtlasCode's changelog and manifest, and have no public changelog, and the Atlassian CLI changelog stops at v1.3.15 while its repository serves 1.3.39 (2). Rovo Dev has been rolling out as a product since October 2025, but the version number carries no stability signal and Atlassian has announced that the standalone product will reach end of life. Judgement call (5). The CLI runs against Atlassian's hosted service, and the Rovo status page has no Rovo Dev component. 20+0+8+2+5 = 35.\n- Verdent (43): Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.\n\n### Transparency \u0026 trust: Rovo Dev CLI +8\n\n- Rovo Dev CLI (63): Proprietary, with clear terms. The Atlassian Customer Agreement (effective 1 October 2026) and the AI Terms (effective 17 August 2026), which say Input and Output are Customer Data and that subcontractors may not train on them (15). The Rovo privacy page keeps Chat and agent inputs and outputs for 30 days and says Rovo has SOC 2, ISO 27001 and data residency, while the Rovo Dev rollout page (modified 27 August 2026) says Rovo Dev has none of the three. We found no retention period for Rovo Dev sessions sent to Atlassian (12). The licensing FAQ promises at least 60 days' notice before Rovo Dev's end of life and dates the Code Reviewer move to 3 December 2026, but gives no date for the CLI's move to the Rovo CLI. Each Atlassian CLI version is supported for six months (14). No telemetry description or opt-out for the CLI was found. AtlasCode's changelog documents Rovo Dev telemetry events in the IDE, which this listing doesn't cover (0). 15+12+14+0 = 41.\n- Verdent (55): Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.\n\n### Payments \u0026 pricing: Verdent +5\n\n- Rovo Dev CLI (15): 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.\n- Verdent (20): Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.\n\n## Score by category\n\n| Category | Weight | Rovo Dev CLI | Verdent | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 43 | Verdent +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 45 | 55 | Verdent +10 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 35 | Rovo Dev CLI +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 33 | Rovo Dev CLI +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 20 | Verdent +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 61 | 61 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 55 | Rovo Dev CLI +8 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **44.1 · E** | **39.7 · E** | |\n\n## Facts side by side\n\n| Fact | Rovo Dev CLI | Verdent |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Atlassian | Verdent AI, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| Last release | 2026-10-16 | 2026-10-29 |\n| Terms last updated | no date given | 2026-05-25 |\n| Privacy policy last updated | couldn't be read | 2026-05-26 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | 2/5 (4) | none |\n\n## How the scores have moved\n\n### Rovo Dev CLI\n\n- +0.2 on 27 October 2026: checklist\n\n### Verdent\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**Verdent.** A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.\n\n## Before you call either\n\n### Rovo Dev CLI\n\n1. 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\n2. Use `acli rovodev serve \u003cport\u003e` and stream `/v3/stream_chat?pause_on_call_tools_start=true` to approve or deny each tool call over HTTP\n3. Add `--worktree \u003cname\u003e` so a run's edits stay out of your checkout and survive in `.rovodev/worktrees/\u003cname\u003e`\n4. Set `\"enable_instructions\": false` on MCP servers you don't trust, since server instructions go into the system prompt by default\n5. Check `/usage` before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on\n\n### Verdent\n\n1. Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode\n2. Start large changes in Plan Mode and review plan.md before switching to Agent Mode\n3. Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape\n4. Keep work under git, since rollback relies on git and there is no sandbox\n5. Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026\n\n## Questions\n\n### Which is better for AI agents, Rovo Dev CLI or Verdent?\n\nRovo Dev CLI scores 44.1 (E) on agent readiness against Verdent's 39.7 (E), and leads in 3 of 7 scored categories. Verdent leads on reliability, schema \u0026 documentation and payments \u0026 pricing.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"rovo-dev-cli\", \"b\": \"verdent\"}`. From a terminal: `anchor compare rovo-dev-cli verdent`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/rovo-dev-cli.json and https://www.anchorterminal.com/api/v1/tools/verdent.json\n\n## Other comparisons with Rovo Dev CLI or Verdent\n\n- [Agent Zero vs Rovo Dev CLI](https://www.anchorterminal.com/compare/agent-zero-vs-rovo-dev-cli.md)\n- [Agent Zero vs Verdent](https://www.anchorterminal.com/compare/agent-zero-vs-verdent.md)\n- [Aider vs Rovo Dev CLI](https://www.anchorterminal.com/compare/aider-vs-rovo-dev-cli.md)\n- [Aider vs Verdent](https://www.anchorterminal.com/compare/aider-vs-verdent.md)\n- [Amp vs Rovo Dev CLI](https://www.anchorterminal.com/compare/amp-vs-rovo-dev-cli.md)\n- [Amp vs Verdent](https://www.anchorterminal.com/compare/amp-vs-verdent.md)\n- [Antigravity CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-rovo-dev-cli.md)\n- [Antigravity CLI vs Verdent](https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent.md)\n- [Auggie CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/auggie-vs-rovo-dev-cli.md)\n- [Auggie CLI vs Verdent](https://www.anchorterminal.com/compare/auggie-vs-verdent.md)\n- [AXLR vs Rovo Dev CLI](https://www.anchorterminal.com/compare/axlr-vs-rovo-dev-cli.md)\n- [AXLR vs Verdent](https://www.anchorterminal.com/compare/axlr-vs-verdent.md)\n- [Claude Code vs Rovo Dev CLI](https://www.anchorterminal.com/compare/claude-code-vs-rovo-dev-cli.md)\n- [Claude Code vs Verdent](https://www.anchorterminal.com/compare/claude-code-vs-verdent.md)\n- [Cline vs Rovo Dev CLI](https://www.anchorterminal.com/compare/cline-vs-rovo-dev-cli.md)\n- [Cline vs Verdent](https://www.anchorterminal.com/compare/cline-vs-verdent.md)\n- [Conductor vs Rovo Dev CLI](https://www.anchorterminal.com/compare/conductor-vs-rovo-dev-cli.md)\n- [Conductor vs Verdent](https://www.anchorterminal.com/compare/conductor-vs-verdent.md)\n- [Crush vs Rovo Dev CLI](https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.md)\n- [Crush vs Verdent](https://www.anchorterminal.com/compare/crush-vs-verdent.md)\n- [Cursor CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-rovo-dev-cli.md)\n- [Cursor CLI vs Verdent](https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.md)\n- [DeepSeek Harness (dsh) vs Rovo Dev CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-rovo-dev-cli.md)\n- [DeepSeek Harness (dsh) vs Verdent](https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent.md)\n- [dsh-superagent (DeepSeek) vs Rovo Dev CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli.md)\n- [dsh-superagent (DeepSeek) vs Verdent](https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent.md)\n- [Devin vs Rovo Dev CLI](https://www.anchorterminal.com/compare/devin-vs-rovo-dev-cli.md)\n- [Devin vs Verdent](https://www.anchorterminal.com/compare/devin-vs-verdent.md)\n- [Droid CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/droid-cli-vs-rovo-dev-cli.md)\n- [Droid CLI vs Verdent](https://www.anchorterminal.com/compare/droid-cli-vs-verdent.md)\n- [Pi vs Rovo Dev CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-rovo-dev-cli.md)\n- [Pi vs Verdent](https://www.anchorterminal.com/compare/earendil-pi-vs-verdent.md)\n- [Emdash vs Rovo Dev CLI](https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli.md)\n- [Emdash vs Verdent](https://www.anchorterminal.com/compare/emdash-vs-verdent.md)\n- [Gemini CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-rovo-dev-cli.md)\n- [Gemini CLI vs Verdent](https://www.anchorterminal.com/compare/gemini-cli-vs-verdent.md)\n- [GitHub Copilot CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-rovo-dev-cli.md)\n- [GitHub Copilot CLI vs Verdent](https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent.md)\n- [goose vs Rovo Dev CLI](https://www.anchorterminal.com/compare/goose-vs-rovo-dev-cli.md)\n- [goose vs Verdent](https://www.anchorterminal.com/compare/goose-vs-verdent.md)\n- [Harness² vs Rovo Dev CLI](https://www.anchorterminal.com/compare/harness2-vs-rovo-dev-cli.md)\n- [Harness² vs Verdent](https://www.anchorterminal.com/compare/harness2-vs-verdent.md)\n- [HarnessRouter vs Rovo Dev CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli.md)\n- [HarnessRouter vs Verdent](https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.md)\n- [Jules vs Rovo Dev CLI](https://www.anchorterminal.com/compare/jules-vs-rovo-dev-cli.md)\n- [Jules vs Verdent](https://www.anchorterminal.com/compare/jules-vs-verdent.md)\n- [Junie CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/junie-vs-rovo-dev-cli.md)\n- [Junie CLI vs Verdent](https://www.anchorterminal.com/compare/junie-vs-verdent.md)\n- [Kilo Code CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-rovo-dev-cli.md)\n- [Kilo Code CLI vs Verdent](https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent.md)\n- [Kimi Code CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli.md)\n- [Kimi Code CLI vs Verdent](https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent.md)\n- [Kiro CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.md)\n- [Kiro CLI vs Verdent](https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.md)\n- [Letta vs Rovo Dev CLI](https://www.anchorterminal.com/compare/letta-vs-rovo-dev-cli.md)\n- [Letta vs Verdent](https://www.anchorterminal.com/compare/letta-vs-verdent.md)\n- [mini-swe-agent vs Rovo Dev CLI](https://www.anchorterminal.com/compare/mini-swe-agent-vs-rovo-dev-cli.md)\n- [mini-swe-agent vs Verdent](https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent.md)\n- [MiniMax Code vs Rovo Dev CLI](https://www.anchorterminal.com/compare/minimax-code-vs-rovo-dev-cli.md)\n- [MiniMax Code vs Verdent](https://www.anchorterminal.com/compare/minimax-code-vs-verdent.md)\n- [Mistral Vibe CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-rovo-dev-cli.md)\n- [Mistral Vibe CLI vs Verdent](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent.md)\n- [Muse Code vs Rovo Dev CLI](https://www.anchorterminal.com/compare/muse-code-vs-rovo-dev-cli.md)\n- [Muse Code vs Verdent](https://www.anchorterminal.com/compare/muse-code-vs-verdent.md)\n- [OpenAI Agents API vs Rovo Dev CLI](https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli.md)\n- [OpenAI Agents API vs Verdent](https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent.md)\n- [OpenAI Codex vs Rovo Dev CLI](https://www.anchorterminal.com/compare/openai-codex-vs-rovo-dev-cli.md)\n- [OpenAI Codex vs Verdent](https://www.anchorterminal.com/compare/openai-codex-vs-verdent.md)\n- [OpenCode vs Rovo Dev CLI](https://www.anchorterminal.com/compare/opencode-vs-rovo-dev-cli.md)\n- [OpenCode vs Verdent](https://www.anchorterminal.com/compare/opencode-vs-verdent.md)\n- [OpenHands vs Rovo Dev CLI](https://www.anchorterminal.com/compare/openhands-vs-rovo-dev-cli.md)\n- [OpenHands vs Verdent](https://www.anchorterminal.com/compare/openhands-vs-verdent.md)\n- [Orca vs Rovo Dev CLI](https://www.anchorterminal.com/compare/orca-vs-rovo-dev-cli.md)\n- [Orca vs Verdent](https://www.anchorterminal.com/compare/orca-vs-verdent.md)\n- [Paseo vs Rovo Dev CLI](https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli.md)\n- [Paseo vs Verdent](https://www.anchorterminal.com/compare/paseo-vs-verdent.md)\n- [Prime Agent vs Rovo Dev CLI](https://www.anchorterminal.com/compare/prime-agent-vs-rovo-dev-cli.md)\n- [Prime Agent vs Verdent](https://www.anchorterminal.com/compare/prime-agent-vs-verdent.md)\n- [Qoder CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/qoder-cli-vs-rovo-dev-cli.md)\n- [Qoder CLI vs Verdent](https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.md)\n- [Qwen Code vs Rovo Dev CLI](https://www.anchorterminal.com/compare/qwen-code-vs-rovo-dev-cli.md)\n- [Qwen Code vs Verdent](https://www.anchorterminal.com/compare/qwen-code-vs-verdent.md)\n- [Mirror CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/reflection-mirror-vs-rovo-dev-cli.md)\n- [Mirror CLI vs Verdent](https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.md)\n- [Rovo Dev CLI vs Sculptor](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-sculptor.md)\n- [Rovo Dev CLI vs T3 Code](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code.md)\n- [Rovo Dev CLI vs Traycer](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-traycer.md)\n- [Rovo Dev CLI vs Unstoppable](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-unstoppable.md)\n- [Rovo Dev CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-vibe-trading.md)\n- [Rovo Dev CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-warp.md)\n- [Sculptor vs Verdent](https://www.anchorterminal.com/compare/sculptor-vs-verdent.md)\n- [T3 Code vs Verdent](https://www.anchorterminal.com/compare/t3-code-vs-verdent.md)\n- [Traycer vs Verdent](https://www.anchorterminal.com/compare/traycer-vs-verdent.md)\n- [Verdent vs Vibe-Trading](https://www.anchorterminal.com/compare/verdent-vs-vibe-trading.md)\n- [Verdent vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/verdent-vs-warp.md)\n- [Clawboo vs Rovo Dev CLI](https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.md)\n- [Clawboo vs Verdent](https://www.anchorterminal.com/compare/clawboo-vs-verdent.md)\n- [CLI Manager vs Rovo Dev CLI](https://www.anchorterminal.com/compare/cli-manager-vs-rovo-dev-cli.md)\n- [CLI Manager vs Verdent](https://www.anchorterminal.com/compare/cli-manager-vs-verdent.md)\n- [Harness vs Rovo Dev CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-rovo-dev-cli.md)\n- [Harness vs Verdent](https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent.md)\n- [OpenMausBot vs Rovo Dev CLI](https://www.anchorterminal.com/compare/openmausbot-vs-rovo-dev-cli.md)\n- [OpenMausBot vs Verdent](https://www.anchorterminal.com/compare/openmausbot-vs-verdent.md)\n- [Paperclip vs Rovo Dev CLI](https://www.anchorterminal.com/compare/paperclip-vs-rovo-dev-cli.md)\n- [Paperclip vs Verdent](https://www.anchorterminal.com/compare/paperclip-vs-verdent.md)\n- [Parallax vs Rovo Dev CLI](https://www.anchorterminal.com/compare/parallax-agents-vs-rovo-dev-cli.md)\n- [Parallax vs Verdent](https://www.anchorterminal.com/compare/parallax-agents-vs-verdent.md)\n- [Unstoppable vs Verdent](https://www.anchorterminal.com/compare/unstoppable-vs-verdent.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Rovo Dev CLI vs Verdent", "url": "" } ], "description": "Rovo Dev CLI scores 44.1 (E) to Verdent's 39.7 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Rovo Dev CLI E 44.1", "Verdent E 39.7", "scores" ], "h1": "Rovo Dev CLI vs Verdent", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/rovo-dev-cli-vs-verdent", "published": "2026-10-01", "section": "tools", "title": "Rovo Dev CLI vs Verdent for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent" }, "tokens": { "markdown": 7100, "slim": 3380 }, "version": 1 }