# Rovo Dev CLI vs T3 Code (slim)

> T3 Code scores 51.9 (D) 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/rovo-dev-cli-vs-t3-code.md (~6,550 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code
- 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)

T3 Code scores 51.9 (D) on agent readiness against Rovo Dev CLI's 44.1 (E), and leads in 5 of 7 scored categories. Rovo Dev CLI leads on security & auth and transparency & trust. Both do agent harnesses.

- Rovo Dev CLI: E 44.1, rank #1217 of 1486 · https://www.anchorterminal.com/tools/rovo-dev-cli.min.md
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.min.md
- 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. Ahead on Security & auth, 48 against 35; Transparency & trust, 63 against 51.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Ahead on Reliability, 43 against 35; Schema & documentation, 55 against 45; Agent ergonomics, 60 against 53; Payments & pricing, 60 against 15; Maintenance & community, 75 against 61. Also No key needed to call it; Open source.

| Category | Rovo Dev CLI | T3 Code |
| --- | --- | --- |
| Reliability (16%) | 35 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 45 | 55 |
| Agent ergonomics (13%) | 53 | 60 |
| Security & auth (14%) | 48 | 35 |
| Payments & pricing (10%) | 15 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 75 |
| Transparency & trust (7%) | 63 | 51 |

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

Why the edge:
- Payments & pricing, T3 Code +45: 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.); T3 Code 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.)
- Maintenance & community, T3 Code +14: 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.); T3 Code 75 (Commits and nightly tags on 6 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 official apps and install script (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Security & auth, Rovo Dev CLI +13: 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.); T3 Code 35 (Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.)
- Transparency & trust, Rovo Dev CLI +12: 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.); T3 Code 51 (MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.)
- Schema & documentation, T3 Code +10: 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.); T3 Code 55 (Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55).)
- Reliability, T3 Code +8: 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.); T3 Code 43 (Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run 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). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.)