Back to Devoured - June 11, 2026
DEVOURED
Faster Code Review with Cursor's Bugbot

Faster Code Review with Cursor's Bugbot

AI Cursor
Cursor's Bugbot update enables sub-three-minute reviews by utilizing Composer 2.5 and improved internal harnesses.
What: The update reduces Bugbot run times by 3x and costs by 22%, while enabling users to run security reviews locally before pushing code via the /review command.
Why it matters: Shortening the feedback loop in code reviews is critical for keeping AI-augmented development workflows fast and preventing context switching.
Takeaway: Run `/review-bugbot` or `/review-security` locally before your next pull request to catch bugs before they hit CI.
Deep dive
  • 90% of Bugbot runs now complete in under three minutes.
  • New /review command runs agents locally before pushing code.
  • Integration with GitHub/GitLab: Bugbot skips re-reviewing unchanged diffs in PRs.
  • Performance improvements driven by harness optimization and the underlying Composer 2.5 model.
Original article

Today we're shipping our biggest set of improvements yet to Bugbot.

Bugbot is now over 3x faster to run, 22% cheaper, and finds 10% more bugs per review. In practice, 90% of Bugbot runs now finish in under three minutes.

A faster, less expensive, more thorough Bugbot allows you to find issues sooner and merge code faster.

Run Bugbot before you push

You can now run Bugbot and Security Review with /review before pushing code. /review prompts you to choose which agents to run, or use /review-bugbot and /review-security directly.

This is a great way to catch and fix issues before pushing the code.

/review also syncs with Bugbot on GitHub and GitLab. If you run /review and then open a PR with the same diff, Bugbot recognizes it, skips the review, and leaves a comment noting it has already reviewed that diff.

Available in Cursor 3.7+ and on cursor.com/agents, with support in CLI coming soon.

Only review what's new in your PR

Bugbot by default re-reviews the entire PR every time a change is pushed. This can result in new flags on code it had already reviewed and approved. You can now configure Bugbot to only review what's new since the last review, keeping feedback focused on your latest updates.

How we got here

These performance gains are made possible by harness improvements and progress we've made training Composer 2.5, which now powers Bugbot. Our model training work is one part of how we will continue to improve Bugbot over time.

Bugbot respects model block lists. If your organization has opted out of Composer 2.5, Bugbot will automatically fall back to the next best available model. Speed and performance can vary depending on your configuration.

Learn more

Try Bugbot here and read the Bugbot docs to learn more.

Explore all 55 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi