Cursor’s Bugbot now finishes a code review in ~90 seconds, down from ~5 minutes. That’s a 3x speed improvement alongside a 22% price cut and 10% more bugs caught per review — from 0.56 to 0.62 bugs per review on average.
The update ships three changes at once:
- 3x faster reviews — average time drops from ~5 minutes to ~90 seconds, which makes Bugbot viable as a blocking CI check rather than something you fire and forget
- 22% cheaper — relevant at Bugbot’s $40/user/month price point, where team costs add up fast
- 10% more bugs per review — the detection rate bump means fewer logic and security issues slipping through to main
/reviewcommand — run Bugbot locally inside Cursor before pushing, so you catch issues before they hit the PR
The /review command is the most interesting addition. Previously, Bugbot only ran as a GitHub integration triggered on pull requests. Now you can invoke it mid-workflow, which turns it from a CI gate into something closer to a linter you run on demand. One early user on X called it the feature they’d wanted since Bugbot launched.
NOTE
Bugbot still runs as a GitHub-integrated reviewer on PRs. The /review command adds a local option — it doesn’t replace the automated flow.
At $40/user/month, Bugbot sits at a price point where speed and accuracy directly affect whether teams keep it. A 5-minute review was slow enough to ignore; 90 seconds is fast enough to block merges on. Alternatives like cubic compete on deeper codebase analysis, but Cursor’s tight IDE integration — including a “Fix in Cursor” button on flagged issues — keeps the feedback loop short.
Available now for all Bugbot subscribers. The /review command works in the latest stable Cursor release.