Do coding agents recommend Qodo Merge?
Qodo Merge was chosen in 8% of 290 judged code review sessions, ranking fifth. Measured with Claude Code, Codex and Cursor.
Qodo Merge was chosen in 8% of 290 judged code review sessions, ranking fifth. It was also raised as a candidate in 39 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 Qodo Merge. What an agent actually installed.
The numbers
| Category | Code review |
| Sessions in the category | 290 |
| Sessions where Qodo Merge was chosen | 24 |
| Install share | 8% |
| Rank in category | 5 of 10 |
| Codebases it won in | 4 |
| Raised as a candidate, not chosen | 39 |
| Chosen when considered | 38% |
| Site | qodo.ai |
By agent
The three agents treat Qodo Merge very differently. Codex chose it in 16% of its sessions in this category and Cursor in 0%, a spread of 16 points.
| Agent | Sessions | Chose Qodo Merge | Share |
|---|---|---|---|
| Claude Code | 100 | 8 | 8% |
| Codex | 100 | 16 | 16% |
| Cursor | 90 | 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 8%.
By who was asking
Qodo Merge does much better with one kind of buyer than another. It won 16% of sessions asked as junior developer and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Qodo Merge | Share |
|---|---|---|---|
| Vibe coder | 58 | 1 | 2% |
| Junior developer | 116 | 18 | 16% |
| Senior engineer | 58 | 0 | 0% |
| Enterprise team | 58 | 5 | 9% |
What Qodo Merge was up against
The full ranking in code review, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Claude Code review | 76 | 26% |
| 2 | Cursor Bugbot | 71 | 24% |
| 3 | Codex code review | 37 | 13% |
| 4 | CodeRabbit | 34 | 12% |
| 5 | Qodo Merge (this page) | 24 | 8% |
| 6 | Built in-house (no product adopted) | 19 | 7% |
| 7 | Semgrep | 10 | 3% |
| 8 | GitHub Copilot code review | 9 | 3% |
What this means
Qodo Merge was raised in 39 sessions and chosen in 24. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
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 Qodo Merge: 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 Qodo Merge?
Yes. Qodo Merge was chosen in 24 of the 290 judged sessions in code review, a 8% install share, ranking fifth in its category.
Does Claude Code recommend Qodo Merge?
In 8 of the 100 sessions in code review run with Claude Code, which is 8%.
Do different coding agents treat Qodo Merge differently?
Yes, and by a wide margin. Codex chose it in 16% of its runs and Cursor 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 Qodo Merge considered but not chosen?
It was raised as a candidate in 39 sessions without being chosen, and chosen in 24. That is a 38% 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.