Rovo Dev CLI Review, Pricing & Alternatives (2026)

Rovo Dev CLI is Atlassian's command line interface for software development tasks, with local repository access and connections to Atlassian work data. Atlassian began rolling it out in October 2025 after beta testing. The service targets teams using Jira Standard or Premium, where administrators can enable the CLI separately from Rovo Dev code reviews. Atlassian now says Rovo Dev is reaching end of life as a standalone product. Its capabilities are moving into eligible Jira and Teamwork Collection subscriptions, and Rovo Dev CLI is becoming Rovo CLI. That gives the current tool a clear practical use, but also makes its name and billing model transitional. Atlassian does not publish a company founding or Rovo Dev user count in these product documents.

A normal session starts with `acli rovodev run`, either interactively or with one instruction for a discrete task. From the terminal, the agent can inspect a repository, explain code, generate documentation, create or refactor files, and run development tasks. Jira commands show connection status, set a global project, apply a workspace-specific project, or disable the integration, helping teams align terminal work with tracked issues. The `--worktree` option isolates changes in a Git worktree, which is useful for parallel experiments or safer reviews. Session controls restore, fork, rename, clear, or prune context. Administrators can configure MCP servers, memory files, saved prompts, hooks, subagents, and permitted directories. Plan and read-only ask modes support review before edits, while model selection, usage reporting, server mode, and an optional IDE plugin extend the workflow.

Rovo Dev uses a selection of available AI models rather than exposing one fixed public model in the cited documentation. Atlassian says consumption depends on the model, context processed, reasoning, and tool use, so a short question and a multistep repository change can draw materially different amounts from the allowance. The CLI supports model switching, subagents, MCP servers, worktrees, sessions, hooks, and research commands, giving teams options for isolating changes, reusing context, and extending tool access. Administrators therefore need to monitor usage rather than estimate capacity from request counts alone. Atlassian’s successor, Rovo CLI, adds Teamwork Graph access across Jira, Confluence, Bitbucket, Loom, Atlas goals, projects, and connected applications. Migration changes `acli rovodev` to `rovo`, `.rovodev` to `.rovo`, and Rovo Dev credits to Rovo credits, so scripts and cost controls require review.

Rovo Dev Free provides 350 credits per user per month per Jira site where it is activated at no extra cost. Atlassian says that allowance typically covers one to ten CLI tasks, although complex tasks use more credits. When the allowance ends, the CLI stops working until the next billing cycle. Rovo Dev Standard costs $20 per developer monthly and provides 2,000 credits per month at the Atlassian organization level. Those credits can be used across qualifying sites in that organization. If an administrator enables extra usage, additional credits cost $0.01 each. Atlassian says 2,000 credits typically cover five to 50 CLI tasks, with actual consumption varying by task complexity.

The largest limitation is the product transition. Atlassian says standalone Rovo Dev is ending, while the move to Rovo CLI changes commands, settings, authentication, and credit accounting. Teams evaluating it should therefore test migration procedures before standardizing scripts, configuration files, or onboarding documentation. The rollout documentation says Rovo Dev does not support data residency, is not HIPAA compliant, and has not yet been externally audited for ISO 27001 or SOC 2 compliance. The free allowance can support initial trials, but usage stops when 350 credits are exhausted; Standard costs $20 per developer monthly for 2,000 organization-level credits, with extra usage priced at $0.01 per credit. GitHub Copilot CLI, Claude Code, and Aider offer different terminal approaches. Rovo Dev suits Jira-centered teams willing to manage transition risk and needing Atlassian context inside development sessions.