From the experiment

Do coding agents recommend Claude Code review?

Claude Code review is the most chosen code review tool, taking 26% of 290 judged code review sessions. Measured with Claude Code, Codex and Cursor.

Published September 8, 2026 Read as Markdown

Claude Code review is the most chosen code review tool, taking 26% of 290 judged code review sessions. It was also raised as a candidate in 4 further sessions without being chosen.

This page reports what happened when Claude Code, Codex and Cursor 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

CategoryCode review
Sessions in the category290
Sessions where Claude Code review was chosen76
Install share26%
Rank in category1 of 10
Codebases it won in9
Raised as a candidate, not chosen4
Chosen when considered95%
Siteanthropic.com

By agent

The three agents treat Claude Code review very differently. Claude Code chose it in 76% of its sessions in this category and Codex in 0%, a spread of 76 points.

AgentSessionsChose Claude Code reviewShare
Claude Code1007676%
Codex10000%
Cursor9000%

A single blended install share would report the midpoint and hide both ends. If most of your users run Codex, your real position here is 0%, not 26%.

By who was asking

Claude Code review performs similarly across the four kinds of buyer, from 22% to 34%. That is unusual: the category leader changed with the persona in 17 of the 21 categories we measured.

Who is askingSessionsChose Claude Code reviewShare
Vibe coder582034%
Junior developer1162622%
Senior engineer581322%
Enterprise team581729%

What Claude Code review was up against

The full ranking in code review, from the same sessions:

#ProductRuns wonShare
1Claude Code review (this page)7626%
2Cursor Bugbot7124%
3Codex code review3713%
4CodeRabbit3412%
5Qodo Merge248%
6Built in-house (no product adopted)197%
7Semgrep103%
8GitHub Copilot code review93%

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 290 sessions in code review are part of a published set of 5,915, 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 76 of the 290 judged sessions in code review, a 26% install share, ranking first in its category.

Does Claude Code recommend Claude Code review?

In 76 of the 100 sessions in code review run with Claude Code, which is 76%.

Do different coding agents treat Claude Code review differently?

Yes, and by a wide margin. Claude Code chose it in 76% of its runs and Codex in 0%.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 56 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 4 sessions without being chosen, and chosen in 76. That is a 95% conversion from considered to chosen.

Where this comes from

Armature ran 5,915 judged sessions with Claude Code, Codex and Cursor inside 56 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages