Cursor's Bugbot Is Now 3x Faster, 22% Cheaper, and Finds More Bugs

Cursor shipped a Bugbot performance update on June 10. The numbers are specific: average review time dropped from roughly five minutes to around 90 seconds, cost per run fell 22%, and bug detection improved from 0.56 per review to 0.62. The update is powered by Composer 2.5 and is available in Cursor 3.7 and later.

What Changed

The speed improvement is the most user-visible change. Five minutes is long enough to break context and do something else. Ninety seconds is closer to the window where you can stay focused and act on what the review finds rather than having to context-switch back into it.

The 10% improvement in bug detection is smaller but meaningful if you’re running reviews on every PR. Going from 0.56 to 0.62 bugs per review across a team generating hundreds of PRs a month adds up. The cost reduction makes it more practical to run reviews on every commit rather than reserving them for larger changes.

The /review Command

The update also ships a /review command that runs Bugbot locally before you push. The idea is to turn Bugbot into a pre-push gate rather than something that runs after the PR is already open. You get the results in your terminal, fix what you want to fix, and push a cleaner diff.

Reviews can also be configured to focus only on new changes in the current diff, rather than scanning the full codebase or entire file. For teams with existing codebases that have accumulated issues, this keeps the signal-to-noise ratio higher in daily development.

Context

Bugbot has been through a few changes recently. In May, Cursor moved it from per-seat pricing to usage-based billing with configurable effort levels. The June update is the first major performance improvement since that change, and it suggests Composer 2.5 is doing most of the work — both on speed and accuracy.

Cursor 3.7 is required for the /review command. The performance improvements apply to all Bugbot runs on supported plans.

Source: Cursor changelog