Do coding agents recommend GitHub Copilot code review?
GitHub Copilot code review was chosen in 6% of 526 judged code review sessions, ranking sixth.
GitHub Copilot code review was chosen in 6% of 526 judged code review sessions, ranking sixth. It was also raised as a candidate in 37 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 GitHub Copilot code review. What an agent actually installed.
The numbers
| Category | Code review |
| Sessions in the category | 526 |
| Sessions where GitHub Copilot code review was chosen | 31 |
| Install share | 6% |
| Rank in category | 6 of 21 |
| Codebases it won in | 6 |
| Raised as a candidate, not chosen | 37 |
| Chosen when considered | 46% |
| Site | github.com |
By agent
The agents treat GitHub Copilot code review very differently. Muse Code chose it in 15% of its sessions in this category and Claude Code in 0%, a spread of 15 points.
| Agent | Sessions | Chose GitHub Copilot code review | Share |
|---|---|---|---|
| Claude Code | 130 | 0 | 0% |
| Codex | 160 | 15 | 9% |
| Cursor | 120 | 0 | 0% |
| Grok Build CLI | 30 | 3 | 10% |
| Muse Code | 86 | 13 | 15% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Claude Code, your real position here is 0%, not 6%.
By who was asking
GitHub Copilot code review performs similarly across the four kinds of buyer, from 1% to 15%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose GitHub Copilot code review | Share |
|---|---|---|---|
| Vibe coder | 106 | 16 | 15% |
| Junior developer | 164 | 8 | 5% |
| Senior engineer | 106 | 1 | 1% |
| Enterprise team | 150 | 6 | 4% |
What GitHub Copilot code review was up against
The full ranking in code review, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Claude Code review | 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 (this page) | 31 | 6% |
| 8 | Semgrep | 22 | 4% |
What this means
GitHub Copilot code review was raised in 37 sessions and chosen in 31. 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 526 sessions in code review are part of a published set of 15,287, 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 GitHub Copilot 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 GitHub Copilot code review?
Yes. GitHub Copilot code review was chosen in 31 of the 526 judged sessions in code review, a 6% install share, ranking sixth in its category.
Does Claude Code recommend GitHub Copilot code review?
In 0 of the 130 sessions in code review run with Claude Code, which is 0%.
Do different coding agents treat GitHub Copilot code review differently?
Yes, and by a wide margin. Muse Code chose it in 15% of its runs and Claude Code in 0%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 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 GitHub Copilot code review considered but not chosen?
It was raised as a candidate in 37 sessions without being chosen, and chosen in 31. That is a 46% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.