How Code Reviewer uses Rovo credits

Starting in early November 2026, Code Reviewer, previously Rovo Dev code reviews, will be available with a paid Jira or Teamwork Collection subscription. You won't need a separate Rovo Dev subscription to use it.

With this transition, Code Reviewer will use Rovo credits under our usage-based pricing model. Rovo credit billing will not start until December 3, 2026. The credits come from your organization's shared allowance, which is the same pool used by Rovo Chat, Rovo agents, and other AI features. Your use of Code Reviewer is subject to the Atlassian Acceptable Use Policy.

Whose credits a review uses

Each review uses Rovo credits from your organization's shared pool. Find out how Rovo credit allowances work

When do reviews run

How often Code Reviewer runs depends on the review option set for each repository:

• Every commit

• Every new pull request

• Manual trigger only (default)

With Code Reviewer, the default option is Manual trigger only. With this option, Code Reviewer doesn't use credits in a repository until someone either starts a review or sets the review option to an automated schedule. If a repository already runs reviews automatically, it keeps its current option.

If you're not sure which to pick, you can try starting with Every new pull request. Each new pull request gets feedback, without needing a manual trigger or a fresh review on each commit.

Find out how to trigger a code review and how each option works

What affects how many credits a review uses

Each review uses a variable number of credits, based on how much work Code Reviewer does to understand and review the change. A review uses more credits when Code Reviewer has more to read and reason about:

• Size of the pull request. Bigger changes take more work to review.

• How often reviews run. When code reviews are set to trigger on every commit, every push to an open pull request starts another review.

• Size of the repository. In a large repository, Code Reviewer may read more of the surrounding code to understand a change.

• Your instructions and skills. Code Reviewer reads your custom instructions and Agent Skills on every review, so long instructions and skills add to the cost of each one.

How far your allowance goes

Rovo credits are pooled across your organization, so the number of reviews you can run depends on how many users your subscriptions cover and how much your teams use other Rovo features.

Find out about Rovo credit allowances included in your plan.

Ways to reduce credit usage

• Keep pull requests small and focused on one change.

• Only turn on automatic reviews in the repositories that need them. How to activate code reviews in your repository.

• Use Every new pull request unless a team needs a review after every commit.

• Keep custom instructions short and specific to what you want checked.

Track your usage

Organization admins and billing admins can see Rovo credit usage, including Code Reviewer, in Atlassian Administration.

To find out more about allowances, pay-as-you-go usage and what happens when your organization reaches its limit, see how Rovo credits work.

For developers

Code Reviewer still leaves its feedback as comments on your pull requests in Bitbucket Cloud or GitHub, and you can still start a review yourself when your repository allows it. The credits for each review come from your organization's shared pool.