Do coding agents recommend Claude Code review?
Claude Code review is the most chosen code review tool, taking 19% of 526 judged code review sessions.
Claude Code review is the most chosen code review tool, taking 19% of 526 judged code review sessions. It was also raised as a candidate in 5 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in code review inside a realistic codebase. Not what a chat assistant says about Claude Code review. What an agent actually installed.
The numbers
| Category | Code review |
| Sessions in the category | 526 |
| Sessions where Claude Code review was chosen | 102 |
| Install share | 19% |
| Rank in category | 1 of 21 |
| Codebases it won in | 9 |
| Raised as a candidate, not chosen | 5 |
| Chosen when considered | 95% |
| Site | anthropic.com |
By agent
The agents treat Claude Code review very differently. Claude Code chose it in 78% of its sessions in this category and Cursor in 0%, a spread of 78 points.
| Agent | Sessions | Chose Claude Code review | Share |
|---|---|---|---|
| Claude Code | 130 | 101 | 78% |
| Codex | 160 | 1 | 1% |
| Cursor | 120 | 0 | 0% |
| Grok Build CLI | 30 | 0 | 0% |
| Muse Code | 86 | 0 | 0% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Cursor, your real position here is 0%, not 19%.
By who was asking
Claude Code review performs similarly across the four kinds of buyer, from 17% to 25%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Claude Code review | Share |
|---|---|---|---|
| Vibe coder | 106 | 26 | 25% |
| Junior developer | 164 | 32 | 20% |
| Senior engineer | 106 | 18 | 17% |
| Enterprise team | 150 | 26 | 17% |
What Claude Code review was up against
The full ranking in code review, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Claude Code review (this page) | 102 | 19% |
| 2 | Cursor Bugbot | 91 | 17% |
| 3 | CodeRabbit | 88 | 17% |
| 4 | Qodo Merge | 55 | 10% |
| 5 | Codex code review | 44 | 8% |
| 6 | Built in-house (no product adopted) | 40 | 8% |
| 7 | GitHub Copilot code review | 31 | 6% |
| 8 | Semgrep | 22 | 4% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 526 sessions in code review are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every code review run can be replayed on the board.
If you work on Claude Code review: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Claude Code review?
Yes. Claude Code review was chosen in 102 of the 526 judged sessions in code review, a 19% install share, ranking first in its category.
Does Claude Code recommend Claude Code review?
In 101 of the 130 sessions in code review run with Claude Code, which is 78%.
Do different coding agents treat Claude Code review differently?
Yes, and by a wide margin. Claude Code chose it in 78% of its runs and Cursor in 0%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Claude Code review considered but not chosen?
It was raised as a candidate in 5 sessions without being chosen, and chosen in 102. That is a 95% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.