How Claude Code Review is billed
Claude Code Review costs have no flat per-review price. Reviews are billed on token usage through usage credits, separately from the usage included in your Team or Enterprise plan, and every review is billed to your organization, not to the developer who opened the pull request or asked for the review. What you spend in a month is the cost of each review multiplied by how many reviews run.
Two details catch admins out. First, the charge lands on your Anthropic bill even if the rest of your company runs Claude Code through Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry. Your cloud budget will not show it. Second, any developer with write access can request a review by commenting @claude review, and that review is billed to the organization too. So the person who controls the bill is not the person who triggers it.
That is why I treat Code Review as its own budget line with its own cap, rather than something that rides on the plan. I call the approach the CCC Review Budget: cap first, pilot second, multiply third, then roll out. The rest of this post walks through each step.
What drives the cost of each review
The cost of one review scales with four things: the review level, the size of the change, the complexity of the surrounding code, and how many candidate issues need verifying. You control the first directly. The other three come from how your team works.
The three review levels
| Level | What it trades | Where I would use it |
|---|---|---|
| Quick | A lighter pass. The fastest level, at the lowest cost | High-traffic repositories, internal tools, anything where a human reviewer is still the main gate |
| Standard | Balanced depth, speed and cost. The default level | Most product repositories |
| Deep | The most thorough pass. Takes the longest and costs the most | Payments, auth, data pipelines, anything where a missed bug is expensive |
An Owner sets one organization default under Review level, and can override it per repository by clicking Edit on that repository's row. A new level only applies to reviews that start after the change, so switching a repository to Quick will not reduce reviews already running.
My recommendation: leave the organization default at Standard and use per-repository overrides in both directions. Push your two or three riskiest repositories up to Deep, and drop the noisy ones to Quick. A single organization-wide Deep setting is the easiest way to spend money on reviews of README changes.
The size of the change is the lever your developers hold. Smaller pull requests cost less per review, and they are easier for humans to review too. If your team ships large pull requests, expect the per-review average to reflect that.
What drives the number of reviews
The number of reviews is set per repository by the Review runs setting. This is the bigger lever, because it multiplies everything above.
Review runs settings and their effect on spend
| Setting | When a review runs | Effect on spend |
|---|---|---|
| Once after PR creation | When a pull request is opened, reopened or marked ready for review | About one review per pull request |
| After every push | On each push to the pull request branch | Cost multiplied by the number of pushes. The default for every new repository |
| Manual (@claude review) | Only when someone comments @claude review | No reviews on open or push |
The default is the trap. A repository you add from the admin page starts at After every push, which runs the most reviews. If your developers push ten times while a pull request is open, that pull request can be reviewed ten times. Change the setting as you add each repository, not after the first invoice.
Comment commands shift those counts:
- @claude review runs one review without subscribing to future pushes.
- @claude review always, in a repository set to Once after PR creation or Manual, subscribes that pull request to push-triggered reviews, so cost accrues on every push after the comment.
- @claude review always in an After every push repository changes nothing, because pushes already trigger reviews.
- Drafts and pull requests from forks are skipped by automatic reviews, so pushes to them add nothing unless someone requests a review by comment.
The draft rule is a cheap habit to teach. If developers open pull requests as drafts while they are still pushing fixes, then mark them ready for review once, a Once after PR creation repository reviews the finished change instead of every intermediate state.
Estimate your spend with a pilot
There is no rate card to multiply against, so the estimate has to come from your own pull requests. Run a small pilot before a wide rollout:
- Set a monthly spend limit for the pilot first (next section).
- Turn on Code Review for a few representative repositories with Review runs set to Once after PR creation or Manual.
- After several reviews have run, read each repository's average cost per review in the Average cost column of the Repositories table, in the Code review section of Admin settings > Claude Code.
- Multiply that average by the number of pull requests the repository opens in a month. For After every push, multiply again by the typical number of pushes per pull request.
Pick the pilot repositories on purpose. One with small, frequent pull requests and one with large, infrequent ones will give you a range rather than a single number, and the range is what you need for a budget. A repository's average moves with the size of its pull requests and with the review level, so if you change the level mid-pilot, the earlier reviews no longer tell you much.
The CCC Review Budget worksheet
| Line | Where the number comes from |
|---|---|
| Average cost per review | Average cost column for the pilot repository, after several reviews |
| Pull requests per month | Your own GitHub history for that repository |
| Pushes per pull request | Only if you plan to run After every push. Your own history again |
| Monthly estimate | Average cost x pull requests, x pushes if every push |
| Cap | The sum across repositories, plus the headroom you choose for busy months |
Set the spend limit before anything else
The monthly limit for Code Review lives at claude.ai/admin-settings/usage, where you configure it for the Claude Code Review service. It applies to the whole organization. Code Review stops running reviews when any one of three things runs out:
What stops reviews
| Limit | What it is | How it recovers |
|---|---|---|
| Code Review spend limit | The monthly limit you set for the Claude Code Review service | Resets at the start of the next billing period, or sooner if you raise it |
| Organization spend limit | Your organization's overall monthly spend limit for usage credits | Raise it on the same page |
| Usage credits balance | Your organization's balance of usage credits | Add credits on the same page |
Reviews also stop once what is left is less than the expected cost of one review. When a review is skipped, developers see a comment on the pull request naming the cause and linking to the usage settings.
Set the Code Review limit separately from the organization limit. If reviews draw on the same pool as everything else, a heavy review month can starve the rest of the organization's usage credits. A dedicated cap means the worst case is reviews pausing, not everything pausing.
Track spend after rollout
The Code Review dashboard at claude.ai/analytics/code-review shows activity across the organization:
What the Code Review dashboard shows
| Section | What it shows |
|---|---|
| PRs reviewed | Daily count of pull requests reviewed over the selected time range |
| Code Review cost | Spend so far this month. Shows an amount only when the current month is selected |
| Feedback | Review comments auto-resolved because a developer addressed the issue |
| Code Review findings | Daily count of findings by severity level |
| Repository breakdown | Per-repository pull requests reviewed, comments resolved and review runs, with estimated cost and a per-PR view |
Two caveats before you hand that dashboard to finance. Cost figures in analytics can differ from your invoice: the repository breakdown is estimated at list price, before discounts or credits, and only covers reviews Claude actually posted on a pull request. For invoice-accurate spend, use your Anthropic bill.
The Feedback card is the one I would watch alongside cost. It counts findings developers actually fixed. A repository with high cost and a low auto-resolved count is the first candidate to move to Quick or Manual. One where reviews keep catching real issues has earned Deep. The Claude Code analytics dashboard covers the rest of the usage reporting.
Cut cost without cutting coverage
- Change every new repository off After every push when you add it. This is the single biggest saving.
- Use Manual for high-traffic repositories and let developers opt pull requests in with @claude review.
- Tell REVIEW.md to skip generated code, lockfiles, vendored dependencies and anything your CI already checks, such as linting. Fewer paths to read and fewer candidate findings to verify means less work per review.
- Teach the draft habit: open as draft, push freely, mark ready once.
- Keep the local /code-review command as the developer pre-flight. It runs inside their own Claude Code session, so the obvious issues are cleared before the billed review starts.
Check eligibility before you plan any of this. Code Review is available on Team and Enterprise plans for repositories on GitHub. It is not available to organizations with Zero Data Retention enabled or with the HIPAA configuration applied, and not yet for organizations using customer-managed encryption keys. If you are on either of those, see Zero Data Retention or Claude Code and HIPAA for what you can use instead.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much does Claude Code Review cost?
There is no flat per-review price. Reviews are billed on token usage through usage credits, and each review's cost depends on the review level, the size of the change, the surrounding code and how many findings need verifying. Run a pilot and read the Average cost column to get your own number.
Is Code Review included in a Team or Enterprise plan?
No. Code Review is available on Team and Enterprise plans, but it is billed through usage credits, separately from the usage your plan includes.
Who pays when a developer comments @claude review?
The organization. Every review is billed to the organization, including ones a developer requests by comment, not to the person who opened or requested it.
How do I cap Claude Code Review spend?
Go to claude.ai/admin-settings/usage and set a monthly limit for the Claude Code Review service. Reviews are skipped when that limit, the organization spend limit or the usage credits balance runs out.
What is the cheapest Review runs setting?
Manual (@claude review) runs no reviews on open or push. Once after PR creation runs roughly one review per pull request. After every push, the default for new repositories, multiplies cost by the number of pushes.
Does Code Review cost show up on my AWS or Google Cloud bill?
No. Code Review costs appear on your Anthropic bill even if your organization uses Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry for other Claude Code features.
Last reviewed by David Iya on November 16, 2026


