| How it works |
| Where the review appears |
✓Private sidebar beside the diff, in your browser |
~Comments on the pull request |
| Who sees the findings |
✓Only the reviewer, until they click post |
~Everyone on the pull request |
| When a review runs |
✓When you click AI Review on the pull request |
~Manual by default. A repository can run on every new pull request or every commit |
| Setup |
✓Browser extension plus a Repository: Read token. No Forge app, webhook, or bot user |
~Paid Jira or Teamwork Collection. No separate Rovo Dev subscription after the November 2026 move |
| Review features |
| Findings |
✓Critical, high, and low issues, each with file and line range |
✓Quality, security, and performance comments on the pull request |
| Quality, security, and best-practice scoring |
✓Scorecard layout with quality, security, and best-practice scores |
—Not described as a scorecard. Comments cover quality, security, and performance |
| Chat and follow-up questions |
✓Suggested follow-up questions, chat, and “generate a comment I can post” |
~Rovo Chat is a separate Rovo feature that shares the same credit pool |
| Custom instructions |
✓Custom review and scoring rules, and custom Review Agents
Loading live limits…
|
✓Custom instructions and Agent Skills, read on every review and counted in the credit cost |
| Pull request size |
✓Lines of change reviewed per pull request, by plan
Loading live limits…
|
~Larger diffs, larger repositories, and longer instructions use more Rovo credits. There is no published flat price per review |
| Platforms and hosting |
| Bitbucket Cloud |
✓bitbucket.org, with an API token. Setup |
✓Comments on Bitbucket Cloud pull requests |
| Bitbucket Data Center |
✓Custom domain plus an HTTP access token. Setup |
—Not listed. Atlassian’s docs name Bitbucket Cloud and GitHub |
| Other git hosts |
✓GitHub, GitLab, and Azure DevOps, including self-managed editions |
~GitHub pull requests, in addition to Bitbucket Cloud |
| Jira requirement |
✓None. ThinkReview is the review product |
~Included with paid Jira or Teamwork Collection. A verified business domain is required to turn Rovo on |
| Private and self-hosted AI |
✓Local Ollama models and a self-hosted Enterprise Gateway |
—Not offered for Code Reviewer. Reviews use Atlassian Rovo |
| Code retention |
✓Zero code retention. Source code is never stored on cloud reviews |
~Runs as an Atlassian cloud feature on the pull request |
| In your editor or assistant |
✓ThinkReview MCP: paste a Bitbucket pull request URL into Cursor, Claude Code, or Copilot |
~Rovo Dev CLI is a separate credit product from Code Reviewer |
| Plans and limits |
| Free option |
✓Free plan with a monthly credit pool and a daily cap
Loading live limits…
|
—Needs a paid Jira or Teamwork Collection subscription. Manual trigger spends nothing until someone starts a review |
| What you pay for |
✓A per-user plan with a monthly credit pool and a daily cap |
~The Jira or Collection seat, then shared Rovo credits. A review does not have a flat dollar price |
| Going past the limit |
✓Optional credit packs
Loading live credit packs…
|
~Extra usage at $0.01 per Rovo credit from 3 Dec 2026, with admin spending limits |