Atlassian Rovo Dev
Last reviewed
May 16, 2026
Sources
25 citations
Review status
Source-backed
Revision
v1 ยท 3,713 words
Improve this article
Add missing citations, update stale details, or suggest a clearer explanation.
Suggest edit
CtrlK
Last reviewed
May 16, 2026
Sources
25 citations
Review status
Source-backed
Revision
v1 ยท 3,713 words
Add missing citations, update stale details, or suggest a clearer explanation.
Atlassian Rovo Dev is an agentic AI coding assistant developed by Atlassian that automates parts of the software development lifecycle, including planning, code generation, code review, and pull-request triage.[1][2] The product moved from open beta to general availability in October 2025 on Jira Standard and Premium plans at no extra cost, and Atlassian publicly markets a paid Rovo Dev Standard plan at $20 per developer per month for higher credit allowances and full Bitbucket and GitHub review integrations.[3][4]
Rovo Dev is distinct from the broader Rovo platform. Rovo is the umbrella name for Atlassian Intelligence features, including enterprise search, chat, and Studio agents that work across Jira, Confluence, Bitbucket, and Jira Service Management.[5] Rovo Dev is the developer-focused product family inside that umbrella, surfaced as a command-line interface, a Visual Studio Code extension, and a hosted code reviewer inside Bitbucket Cloud and GitHub.[1][6] In August 2025 the Rovo Dev CLI took the top spot on the SWE-bench Full leaderboard with a 41.98% resolve rate across 2,294 tasks, drawing attention because Atlassian is not historically associated with frontier AI research.[7]
Atlassian is an Australian software company founded in 2002 by Mike Cannon-Brookes and Scott Farquhar. The company is best known for Jira (issue tracking and project management), Confluence (knowledge base and documentation), and Bitbucket (Git hosting and pull requests), all of which are widely used by software teams. Atlassian began assembling generative AI features into its products under the Atlassian Intelligence brand in 2023, and consolidated those features under the new Rovo brand at the Team '24 customer conference in April 2024.[8]
The original Rovo announcement positioned the product as enterprise search and chat over Atlassian content with optional agentic skills built in Rovo Studio. A year later, at the Team '25 conference in Anaheim from April 8 to 10, 2025, Atlassian expanded the line in two directions. The first was to make Rovo free for all Jira, Confluence, and Jira Service Management users on Premium or Enterprise plans, with a more limited allowance for Standard tier customers.[9] The second was to introduce Rovo Dev as a dedicated developer-facing product, initially as a closed beta and then as an open beta program over the summer of 2025.[10]
The Rovo Dev CLI was announced separately in beta on July 30, 2025 as a command-line interface to the same Rovo Dev agent, and Atlassian published a follow-up post on August 8, 2025 detailing GPT-5 support and the SWE-bench result.[7][11] General availability for the full Rovo Dev product, including Bitbucket and Jira integrations and the new pricing structure, landed in mid-October 2025 after what Atlassian described as "months of beta testing" with feedback from open beta customers.[3]
The naming is worth pulling apart because the two names appear together in Atlassian marketing. Rovo (without "Dev") is the broader Atlassian Intelligence layer: search across Atlassian and connected SaaS sources, a chat interface for that knowledge, and a Studio environment for building custom agents and skills.[5] Rovo agents in the Studio are typically built by non-developers to automate routine knowledge work, such as drafting release notes from Jira tickets or summarizing meeting threads from Confluence.[9]
Rovo Dev is a software-engineering specialization layered on top of Rovo. It exposes the same Teamwork Graph context (issues, pull requests, docs, incidents) but adds tools that read and write source code, run terminal commands, propose pull-request edits, and post review comments. Where Rovo is a chat surface that answers questions, Rovo Dev is an agent that ships code changes. The two products share the same identity and permissions plumbing inside Atlassian Cloud, which means a developer who is provisioned on Rovo Dev does not need a separate Rovo seat to use the general search and chat features.[1][5]
Rovo Dev is hosted by Atlassian and runs against third-party hosted large language models from OpenAI and Anthropic, without using customer inputs or outputs to improve those models.[1] The agent does not run a local model on the developer's machine; the CLI, the IDE extension, and the Bitbucket reviewer are all clients that send prompts and tool calls to Atlassian's Rovo Dev service, which in turn calls the chosen frontier model. The CLI binary is closed-source but distributed for free under a click-through agreement and can be installed from atlassian.com without an Atlassian Cloud subscription, though many features (Jira and Bitbucket context retrieval, posted PR comments, deployment summaries) require a connected Atlassian site.[6][11]
The agent loop is grounded in what Atlassian calls the Teamwork Graph, the company's internal knowledge graph that links Jira work items, Confluence pages, Bitbucket pull requests, Compass components, incidents, and deployment events. Rovo Dev retrieves relevant nodes from that graph to populate its working context, which is why Atlassian's marketing leans on the phrase "king of context" in third-party coverage.[12] A developer asking the agent to implement a Jira ticket will see the agent pull in the ticket description, linked design docs from Confluence, related pull requests on the same component, and recent incidents involving that service before producing a plan.
Rovo Dev is available across four distinct surfaces, each oriented to a different point in the development workflow.
| Surface | Description | Status |
|---|---|---|
| Rovo Dev CLI | Terminal agent installed locally; works inside a Git repository and can run with or without an Atlassian Cloud site connected | GA October 2025; cross-platform binaries[6][11] |
| Rovo Dev in VS Code | Atlassian extension for Visual Studio Code and VS Code-compatible IDEs such as Cursor | GA October 2025[13] |
| Rovo Dev Code Reviewer | Hosted PR reviewer that posts comments on Bitbucket Cloud and GitHub pull requests against acceptance criteria | GA October 2025[2][14] |
| Rovo Dev Agents in Jira | Code Planner, Pipeline Troubleshooter, Deployment Summarizer, and Feature Flag Cleaner skills exposed in Jira and Compass | GA October 2025[15] |
The JetBrains story is more nuanced. As of late 2025 Atlassian had not shipped an official JetBrains plugin, citing an intent to expand IDE support without committing to dates.[13] A community-built open-source project, RovoBridge, wraps the Rovo Dev CLI inside a JetBrains GUI for users who want the experience inside IntelliJ-family IDEs, and the same project also supports VS Code.[13] Atlassian's official position is that VS Code (and forks of VS Code such as Cursor) is the primary IDE target, with the CLI serving as the fallback for everything else.
The Code Reviewer surface deserves its own attention because it is the feature Atlassian most aggressively benchmarks internally. Rovo Dev Code Reviewer is built on top of Anthropic's Claude models, with Claude 3.5 Sonnet cited in early 2025 documentation and newer Claude variants rolled in over the second half of the year, and it watches Bitbucket and GitHub for new pull requests.[16] When a PR opens, the reviewer pulls in the linked Jira ticket's acceptance criteria, runs the agent against the diff, and posts inline comments where the implementation does not match the brief or contains likely issues. Atlassian reported in October 2025 that the reviewer had been used internally across more than 1,900 repositories over the prior year, with internal metrics showing pull-request cycle time falling by 30.8% and human-written review comments falling by 35.6%.[16]
Rovo Dev is model-agnostic but ships defaults selected by Atlassian, with the choice exposed through a /models slash command in the CLI.[7] The supported set has grown over the product's first year:
| Model | Provider | Notes |
|---|---|---|
| Claude 3.5 Sonnet | Anthropic | Powered the original Rovo Dev Code Reviewer in early 2025[16] |
| GPT-5 | OpenAI | Added to the CLI on August 8, 2025; first non-Anthropic frontier model in Rovo Dev[7] |
| Claude Sonnet 4.5 | Anthropic | Available across Rovo Dev surfaces in late 2025[17] |
| Claude Opus 4.5 | Anthropic | Promoted as the "most capable" option in late 2025[17] |
| Claude Haiku 4.5 | Anthropic | Cost-efficient option for routine tasks[17] |
| GPT-5.2 and GPT-5.2-Codex | OpenAI | Added to the CLI in early 2026 alongside Claude Haiku and Opus 4.5[17] |
| Claude Opus 4.6 | Anthropic | Added to Rovo Dev Standard within minutes of Anthropic's public release of the model[18] |
Different models consume different amounts of Rovo Dev credits per turn, weighted roughly by model size and Atlassian's negotiated rates with the provider.[17] Atlassian's general guidance is that Haiku-class and smaller models are appropriate for code search, navigation, and routine refactors, while Opus-class and GPT-5-Codex are recommended for harder planning and multi-file edits.
The table below summarises the main capabilities of Rovo Dev as documented in Atlassian's product pages and rollout posts.
| Capability | Description | Source |
|---|---|---|
| Code generation | Generate code from Jira work items or freeform prompts, scoped to the current repository | Product page[1] |
| Plan-then-edit workflow | Code Planner agent turns Jira tickets into technical plans before the agent writes code | Studio docs[15] |
| Inline AI code review | Rovo Dev Code Reviewer comments on Bitbucket and GitHub pull requests against acceptance criteria | Reviewer blog[16] |
| Pipeline troubleshooting | Read build logs and propose fixes when Bitbucket Pipelines fail | Studio docs[15] |
| Deployment summarisation | Generate human-readable release notes from a deployment's commits and tickets | Studio docs[15] |
| Feature flag cleanup | Identify and remove stale feature flags across a codebase | Studio docs[15] |
| Test generation | Produce unit tests and integration tests for changed code | CLI announcement[11] |
| Documentation generation | Draft README, API, and architecture docs from source code | CLI announcement[11] |
| Teamwork Graph context | Pull Jira, Confluence, Bitbucket, and Compass data into the agent's working context | Product page[1] |
| MCP server support | Connect external Model Context Protocol servers as additional tools | CLI announcement[11] |
| Image and PDF input | Attach images and PDFs to a CLI prompt | GPT-5 update[7] |
| Mid-session model switching | Change the underlying model without losing context | GPT-5 update[7] |
| GitHub support | Read source from GitHub and post PR comments without leaving GitHub | Product page[1] |
| Role-based permissions | Atlassian Cloud admin controls over who can use which Rovo Dev features | CLI announcement[11] |
The Rovo Dev CLI can be used as a standalone tool: a developer installs the binary, signs in, and uses it inside any Git repository without provisioning Jira, Confluence, or Bitbucket.[19] The trade-off is loss of the Teamwork Graph context that powers the more enterprise-flavoured features. In that mode Rovo Dev competes more directly with Claude Code and OpenAI's Codex CLI as a generic terminal coding agent.
The table below lists the supported developer environments and how each one connects to the Rovo Dev service.
| Environment | Type | Notes |
|---|---|---|
| macOS (Apple Silicon, Intel) | CLI binary | Distributed as a downloadable binary from atlassian.com[11] |
| Linux (x86_64, arm64) | CLI binary | Distributed as a downloadable binary[11] |
| Windows | CLI binary | Native Windows support; also runs under WSL2[11] |
| VS Code | IDE extension | Ships as part of the Atlassian extension for VS Code[20] |
| VS Code forks (Cursor, others) | IDE extension | Same extension works on VS Code-compatible editors[13] |
| JetBrains IDEs | Community plugin | RovoBridge open-source project; no official Atlassian plugin as of late 2025[13] |
| Bitbucket Cloud | Hosted | Code Reviewer posts comments on PRs[2] |
| GitHub | Hosted | Code Reviewer reads diffs and posts comments via Atlassian integration[1] |
| Jira Cloud | Hosted | Rovo Dev agents triggered from work items[15] |
| Compass | Hosted | Pipeline Troubleshooter and Deployment Summarizer agents[15] |
Atlassian published the GA pricing structure for Rovo Dev in October 2025 alongside the rollout. The tiers are organised around monthly Rovo Dev credits per developer, with overage billed per credit.
| Tier | Price | Monthly credits | Overage | Notes |
|---|---|---|---|---|
| Rovo Dev Free | $0 | 350 credits per user | Not available | Bundled with Jira Standard and Premium plans during the GA rollout[3] |
| Rovo Dev Standard | $20 per developer per month | 2,000 credits per developer | $0.01 per credit | Includes CLI, IDE extension, Bitbucket and GitHub Code Reviewer, Jira integration, 9/5 regional support[4] |
| Annual and enterprise | Contact sales | Custom | Custom | Available to larger organisations through Atlassian sales[4] |
Credits are denominated in "units of usage based on interactions with specific Rovo Dev AI features," with more capable models and longer agent runs consuming more credits per interaction.[4] Atlassian estimates that 2,000 credits is enough to review 30 to 50 pull requests at typical complexity for a single developer.[4] Larger or more complex tasks, such as multi-file refactors using Claude Opus 4.5, consume more.
Atlassian's headline benchmark result is from August 2025. The Rovo Dev CLI placed first on the SWE-bench Full leaderboard with a 41.98% resolve rate across 2,294 real-world software engineering tasks drawn from public GitHub repositories.[7] SWE-bench is maintained by researchers at Princeton and Stanford and measures how often an agent can resolve a GitHub issue end-to-end such that the project's existing tests pass.
It is worth being precise about which variant of the benchmark this refers to. SWE-bench Full is the full 2,294-task dataset; SWE-bench Verified is a 500-task subset where human annotators have confirmed that each task has a well-specified solution and a reliable test. Atlassian's leaderboard claim is on SWE-bench Full rather than SWE-bench Verified, and that distinction matters because most other vendor results widely cited in the press, including those for Claude Code and Devin, are typically quoted on SWE-bench Verified.[7][21] A high score on SWE-bench Full is still a strong result, since the larger dataset includes noisier tasks where simply identifying what "correct" means is harder.
Atlassian also published internal productivity metrics from the year of beta testing inside its own engineering organisation. Across the more than 1,900 repositories where Rovo Dev Code Reviewer was deployed, pull-request cycle time fell by 30.8% and human-authored review comments fell by 35.6%.[16] These are internal numbers rather than third-party measurements, which limits how much weight readers should put on them, but they are consistent with the broader pattern of organisations reporting double-digit PR cycle time improvements after introducing AI review.
The table below compares Rovo Dev with the most commonly cited terminal and IDE coding agents in 2025 and 2026. Benchmark figures are reported as quoted by each vendor or by independent reviewers; readers should note that not every product reports on the same benchmark variant.
| Feature | Atlassian Rovo Dev | Claude Code | Cursor | GitHub Copilot |
|---|---|---|---|---|
| Vendor | Atlassian | Anthropic | Anysphere | GitHub / Microsoft |
| First release | April 2025 (closed beta), October 2025 GA | February 2025 (preview), May 2025 GA | March 2023 (editor); agent features added 2024 to 2026 | October 2021 (general); coding agent 2024 |
| Primary surfaces | CLI, VS Code extension, Bitbucket and GitHub review bot, Jira agents | Terminal CLI, IDE extensions | Standalone editor (VS Code fork) | IDE extensions, GitHub.com integration, CLI |
| Default model | Claude Opus 4.5 (recommended); user-selectable | Claude Opus or Sonnet (latest) | User-selectable; OpenAI and Anthropic | GPT-class default; switchable |
| Atlassian integration | Native (Jira, Confluence, Bitbucket, Compass) | Via MCP server | Via MCP server | Via apps and extensions |
| Pricing | $20 per dev per month (Standard); free tier on Jira Standard and Premium | $20 per month Pro, $200 per month Max | $20 per month Pro, $40 per month Business | $10 per user per month (Individual), $19 per user per month (Business) |
| SWE-bench leaderboard | 41.98% on SWE-bench Full (Aug 2025)[7] | Reported high score on SWE-bench Verified | n/a (editor, not agent benchmark target) | n/a (editor, not agent benchmark target) |
| Open-source CLI | No (free download, proprietary) | No | No | No |
| MCP support | Client and server[11] | Client and server | Client | Limited |
Industry coverage in late 2025 and early 2026 broadly converges on the view that these tools occupy different niches rather than competing head-on.[12][22] Rovo Dev's distinctive strength is enterprise context: tying agent work back to Jira tickets, Bitbucket PRs, Confluence designs, and incident data in a way that competitors can approximate via MCP servers but not natively. Claude Code is more often picked for raw reasoning on long-running autonomous tasks, Cursor for developers who want their agent inside a full IDE rather than a terminal, and GitHub Copilot for teams already invested in the GitHub ecosystem who want broad and incremental autocomplete rather than aggressive agentic behaviour.[12][22]
A common pattern in 2025 and 2026 reporting is that experienced developers use two or three of these tools rather than one. Cursor or Copilot for in-editor autocomplete, Claude Code or Codex CLI for longer autonomous tasks, and Rovo Dev for tying everything back to Jira and Bitbucket. Atlassian's positioning explicitly leans into this; Rovo Dev marketing materials describe the product as complementary to in-editor assistants rather than as a direct replacement.[22] Rovo Dev does not directly compete with Devin, the fully autonomous engineering agent from Cognition, because Devin operates as a hosted human-replacement service while Rovo Dev is positioned as a collaborator inside the developer's existing workflow.
Reaction to Rovo Dev in trade press and developer communities was mostly positive once the GA release landed, with the SWE-bench Full result giving Atlassian an unexpected technical credibility boost. SiliconANGLE described the October 2025 launch as a "major upgrade" that placed Atlassian in the same conversation as Anthropic and OpenAI on agentic coding, while Constellation Research read the rollout primarily as a pricing and packaging story, noting that bundling Rovo Dev Free into Jira Standard and Premium would put the agent in front of a very large existing customer base with no procurement friction.[10][23]
Within the Atlassian developer community, the most frequent feedback in the open beta period focused on two themes. The first was IDE coverage. Many JetBrains users requested an official plugin to match the VS Code experience, and Atlassian's response (an indefinite "we plan to expand") was widely viewed as a gap.[13] The second was the credit pricing model. The $0.01 per credit overage scheme drew comparisons to API metering, with some users arguing that flat-rate pricing comparable to ChatGPT Plus or Claude Pro would be friendlier to teams that already pay for Jira and Bitbucket seats.[24]
The Code Reviewer surface received the most consistent praise. Internal Atlassian data showing a 30.8% PR cycle time improvement is one data point, but third-party coverage frequently called the review experience the strongest part of the product, partly because it does its work asynchronously without needing developers to change their workflow.[16][22] The CLI's standalone use case (running Rovo Dev outside any Atlassian Cloud subscription) found a small but enthusiastic audience among developers who wanted Claude Opus or GPT-5 access bundled into a single $20 per month seat rather than juggling separate Anthropic and OpenAI bills.[19]
On the skeptical side, several reviewers questioned how durable Atlassian's competitive position would be once Anthropic and OpenAI shipped their own Bitbucket-style integrations through MCP. The argument is that Rovo Dev's deepest moat is access to the Teamwork Graph; if Claude Code or Codex CLI can pull the same Jira and Confluence context through an Atlassian MCP server (Atlassian shipped a Remote MCP Server in 2025), the differentiation narrows to user interface and pricing.[25] Atlassian's counter-argument is that Rovo Dev does more than retrieval; the Code Planner, Pipeline Troubleshooter, and Deployment Summarizer agents are not just context-aware chat but pre-built workflows, and those workflows live inside the same surfaces developers already use.[15]