From the experiment

Do coding agents recommend Cursor Bugbot?

Cursor Bugbot was chosen in 24% of 290 judged code review sessions, ranking second. Measured with Claude Code, Codex and Cursor.

Published September 8, 2026 Read as Markdown

Cursor Bugbot was chosen in 24% of 290 judged code review sessions, ranking second. It was also raised as a candidate in 21 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 Cursor Bugbot. What an agent actually installed.

The numbers

CategoryCode review
Sessions in the category290
Sessions where Cursor Bugbot was chosen71
Install share24%
Rank in category2 of 10
Codebases it won in9
Raised as a candidate, not chosen21
Chosen when considered77%
Sitecursor.com

By agent

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

AgentSessionsChose Cursor BugbotShare
Claude Code10000%
Codex10000%
Cursor907179%

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 24%.

By who was asking

Cursor Bugbot performs similarly across the four kinds of buyer, from 21% to 31%. That is unusual: the category leader changed with the persona in 17 of the 21 categories we measured.

Who is askingSessionsChose Cursor BugbotShare
Vibe coder581831%
Junior developer1162723%
Senior engineer581221%
Enterprise team581424%

What Cursor Bugbot was up against

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

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

What this means

A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed.

The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step.

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 Cursor Bugbot: 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 Cursor Bugbot?

Yes. Cursor Bugbot was chosen in 71 of the 290 judged sessions in code review, a 24% install share, ranking second in its category.

Does Claude Code recommend Cursor Bugbot?

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

Do different coding agents treat Cursor Bugbot differently?

Yes, and by a wide margin. Cursor chose it in 79% of its runs and Claude Code 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 Cursor Bugbot considered but not chosen?

It was raised as a candidate in 21 sessions without being chosen, and chosen in 71. That is a 77% 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