Claude Code vs Rovo Dev CLI: pricing, features and which to choose

Claude Code is Anthropic's agentic coding tool, launched in June 2025. It reads repositories, edits files, runs commands, and operates through the terminal, VS Code, JetBrains, desktop app, and web. The product targets developers working on features, bugs, tests, dependency updates, migrations, and release tasks. Anthropic added Claude Code to enterprise offerings in August 2025 after first making it available through individual accounts. Anthropic does not publish a standalone Claude Code user count or funding figure. The company said in March 2026 that Claude Code's run-rate revenue had surpassed $2.5 billion, although TechCrunch reported that figure as a company statement rather than a user metric. The product remains active, with frequent releases and changing model availability.

A typical session starts in a project directory or connected repository. The developer describes a task, Claude Code examines relevant files, proposes a plan, edits files, runs tests or shell commands, and reports results. It can stage changes, write commit messages, create branches, and open pull requests. Developers can guide behavior with CLAUDE.md files, skills, hooks, permissions, and MCP connections to services such as Jira, Slack, or Google Drive. GitHub Actions and GitLab CI/CD support automated review and issue triage. Desktop and web sessions add visual diff review, parallel cloud tasks, and scheduled work. The agent can spawn subagents, but command approvals, test results, generated edits, and security findings still need engineering review.

Claude Code suits developers who can review diffs, run tests, manage permissions, and control token spending. It is less suitable for unattended production changes, deterministic analysis, or users who only want inline completion. GitHub Copilot CLI offers a closer GitHub-centered alternative, Gemini CLI emphasizes Google's tooling and models, and Cursor remains more editor-centered. Claude Code's strongest case is repository-wide work combining planning, file edits, shell commands, tests, Git, and external tools. Its main tradeoffs are shared subscription limits, changing model access, and the need to inspect generated work. Pick Claude Code if terminal or repository-wide agent workflows matter more than lightweight autocomplete.

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.

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.