Code Review costs and usage changedcode-review-costs
Nearest release: v2.1.301, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 15 Oct 2026 19:23 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+10added
Lines−10removed
From line
2
where the diff opens
First seen
15 Oct 2026
this site's first read of the page
Recorded edits2to this page, all time
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Estimate and cap what your organization spends on Claude Code Review: how reviews are billed through usage credits, what drives cost, and where to track usage.
44
5[Code Review](/docs/en/code-review) has no flat per-review price. What you spend depends on the cost of each review and on how many reviews run:
5[Code Review](/docs/en/code-review.md) has no flat per-review price. What you spend depends on the cost of each review and on how many reviews run:
66
7* **Cost of each review**: scales with the [review level](/docs/en/code-review-setup#set-the-default-review-level), the size of the change, the complexity of the surrounding code, and how many candidate issues need verification
7* **Cost of each review**: scales with the [review level](/docs/en/code-review-setup.md#set-the-default-review-level), the size of the change, the complexity of the surrounding code, and how many candidate issues need verification
88* **Number of reviews**: set by [how often reviews run](#how-often-reviews-run) in each repository
99
1010## Pricing
from line 13
1313
1414### How often reviews run
1515
16A repository you add from the admin page starts at **After every push**, which runs the most reviews. Each repository's [**Review runs** setting](/docs/en/code-review-setup#set-when-reviews-run) decides how many reviews a pull request gets:
16A repository you add from the admin page starts at **After every push**, which runs the most reviews. Each repository's [**Review runs** setting](/docs/en/code-review-setup.md#set-when-reviews-run) decides how many reviews a pull request gets:
1717
1818* **Once after PR creation**: a review runs when the pull request is opened, reopened, or marked ready for review
1919* **After every push**: runs on each push, multiplying cost by the number of pushes
from line 21
2121
2222Comment commands, drafts, and pull requests from forks adjust those counts:
2323
24* **`@claude review always` in Once after PR creation or Manual mode**: [opts the PR into push-triggered reviews](/docs/en/code-review-pull-requests#comment-commands), so additional cost accrues per push after that comment
24* **`@claude review always` in Once after PR creation or Manual mode**: [opts the PR into push-triggered reviews](/docs/en/code-review-pull-requests.md#comment-commands), so additional cost accrues per push after that comment
2525* **`@claude review always` in After every push mode**: pushes already trigger reviews, so the subscription doesn't change per-push cost
2626* **`@claude review`**: runs a single review without subscribing to future pushes
27* **Drafts and pull requests from forks**: [automatic reviews skip both](/docs/en/code-review-pull-requests#review-drafts-and-pull-requests-from-forks), so pushes to them don't add reviews
27* **Drafts and pull requests from forks**: [automatic reviews skip both](/docs/en/code-review-pull-requests.md#review-drafts-and-pull-requests-from-forks), so pushes to them don't add reviews
2828
2929## Estimate your spend
3030
from line 47
4747* **Organization spend limit**: your organization's overall monthly spend limit for usage credits. Raise it on the same page.
4848* **Usage credits balance**: your organization's balance of usage credits. Add credits on the same page.
4949
50Code Review also skips reviews once what's left is less than the expected cost of one review. When a review is skipped, developers see a [comment on the PR](/docs/en/code-review-troubleshooting#review-didn’t-run-and-the-pr-shows-a-budget-message) that names the cause and links to the usage settings.
50Code Review also skips reviews once what's left is less than the expected cost of one review. When a review is skipped, developers see a [comment on the PR](/docs/en/code-review-troubleshooting.md#review-didn’t-run-and-the-pr-shows-a-budget-message) that names the cause and links to the usage settings.
5151
5252To monitor spend, use the [analytics dashboard](#view-usage).
5353
from line 66
6666
6767## Related resources
6868
69* [Set up Code Review](/docs/en/code-review-setup): where to choose the review level and when reviews run in each repository
70* [Read and request reviews on a pull request](/docs/en/code-review-pull-requests): the comment commands, pull requests from forks, and the budget message developers see when a review is skipped
71* [Code Review](/docs/en/code-review): what a review checks and what it posts
72* [Manage costs effectively](/docs/en/costs): spend controls and usage tracking for the rest of Claude Code
69* [Set up Code Review](/docs/en/code-review-setup.md): where to choose the review level and when reviews run in each repository
70* [Read and request reviews on a pull request](/docs/en/code-review-pull-requests.md): the comment commands, pull requests from forks, and the budget message developers see when a review is skipped
71* [Code Review](/docs/en/code-review.md): what a review checks and what it posts
72* [Manage costs effectively](/docs/en/costs.md): spend controls and usage tracking for the rest of Claude Code
7373
No line in this hunk matches that.