# Paseo vs Rovo Dev CLI (slim)

> Paseo scores 62.1 (B) to Rovo Dev CLI's 44.1 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli.md (~6,200 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli.json · canonical https://www.anchorterminal.com/compare/paseo-vs-rovo-dev-cli
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Rovo Dev CLI's 44.1 (E), and leads in every scored category. Both do agent harnesses.

- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- Rovo Dev CLI: E 44.1, rank #1217 of 1486 · https://www.anchorterminal.com/tools/rovo-dev-cli.min.md
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Reliability, 50 against 35; Schema & documentation, 65 against 45; Agent ergonomics, 70 against 53; Security & auth, 58 against 48; Payments & pricing, 60 against 15; Maintenance & community, 75 against 61; Transparency & trust, 68 against 63. Also No key needed to call it; Open source.
- Rovo Dev CLI, good 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.

| Category | Paseo | Rovo Dev CLI |
| --- | --- | --- |
| Reliability (16%) | 50 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 45 |
| Agent ergonomics (13%) | 70 | 53 |
| Security & auth (14%) | 58 | 48 |
| Payments & pricing (10%) | 60 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 61 |
| Transparency & trust (7%) | 68 | 63 |

| Fact (where they differ) | Paseo | Rovo Dev CLI |
| --- | --- | --- |
| Vendor | Mohamed Boudra | Atlassian |
| Auth | None | API key |
| Pricing | Free | Paid |
| Licence | Apache-2.0 | Proprietary, under the Atlassian Customer Agreement (effective 1 October 2026) and the Atlassian AI Terms (effective 17 August 2026). No source is published |
| Last release | 2026-11-07 | 2026-10-16 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | couldn't be read |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Agent reviews | none | 2/5 (4) |

Why the edge:
- Payments & pricing, Paseo +45: Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.); 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.)
- Schema & documentation, Paseo +20: Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).); 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:<port>/docs. That contract is only visible on a running server, and no schema for the SSE events or the config file was published (12). No llms.txt on support.atlassian.com or developer.atlassian.com, and no Markdown twins found (0). The tools page says what allow, ask and deny do, what YOLO mode skips and that MCP tools keep their permissions, and the settings page gives each default. Little says when not to use a mode (12). Permission levels, console output formats and tool names are enumerated in the settings reference with defaults (10). Server mode has curl, Python and JavaScript examples. No exit codes or error responses are documented beyond the post's note that a failed entitlement check disables every endpoint except healthcheck and shutdown (7). The API path is versioned (/v3), but there is no public changelog for Rovo Dev builds (4). 12+0+12+10+7+4 = 45.)
- Agent ergonomics, Paseo +17: Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).); 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.)
- Reliability, Paseo +15: Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.); 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.)
- Maintenance & community, Paseo +14: Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.); Rovo Dev CLI 61 (Atlassian's AtlasCode extension, which downloads the same Rovo Dev binary for the IDE, pinned build 202610.16.1b1 in its pre-release of 16 October 2026, and the Atlassian CLI repository served 1.3.39-stable on 23 September 2026. We didn't run the CLI to read the version it installs. Judgement call (30). AtlasCode pinned eight Rovo Dev builds between 23 July and 16 October 2026 (20). No public changelog for the builds. Support is through Atlassian Support and the community, where the Rovo Dev board was last active on 16 January 2026 (5). No SDK and no registry entry. The server-mode API is kept current for the IDE extension (3). The Homebrew formula carries checksums and the Linux repositories are signed. There's no public CI (3). 30+20+5+3+3 = 61.)
- Security & auth, Paseo +10: Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.); 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.)