Bugbot Gets Major Speed and Cost Upgrades

Cursor's Bugbot sees major speed, cost, and detection upgrades, making AI code review faster and more efficient.

Jun 10 at 7:01 PM7 min read

Screenshot of Bugbot interface showing performance metrics. — Bugbot's latest update enhances speed, cost-efficiency, and bug detection capabilities.· Cursor Blog

Visual TL;DR. Bugbot Speed/Cost Upgrades leads to Improved Bug Detection. Bugbot Speed/Cost Upgrades powered by Composer 2.5. Improved Bug Detection enables Faster Development Cycles. Faster Development Cycles facilitated by Run Bugbot Before Push. Run Bugbot Before Push results in Reduced Post-Merge Issues. Bugbot Speed/Cost Upgrades achieves 90% Under 3 Minutes.

Bugbot Speed/Cost Upgrades: AI code review now over 3x faster and 22% cheaper
Improved Bug Detection: Identifies 10% more bugs during code reviews
Composer 2.5: Under the hood technology driving performance enhancements
Faster Development Cycles: Enables quicker integration of code changes
Run Bugbot Before Push: New /review command for preemptive code scanning
Reduced Post-Merge Issues: Catching errors earlier minimizes production problems
90% Under 3 Minutes: Most runs complete quickly for immediate developer feedback

Visual TL;DRQuickExplainDeeper

Cursor's AI code assistant, Bugbot, has received its most significant update yet, promising substantial improvements in speed, cost, and bug detection. According to the Cursor Blog, the tool is now more than three times faster, 22% cheaper, and identifies 10% more bugs during code reviews. This translates to faster development cycles and potentially fewer post-merge issues.

Ninety percent of Bugbot runs now complete in under three minutes, a critical metric for developers seeking immediate feedback. The enhanced Bugbot performance improvements aim to accelerate code integration by finding issues earlier.

Run Bugbot Before You Push

A new command, /review, allows developers to initiate Bugbot and Security Review checks before committing code. Users can select specific agents or run Bugbot and Security Review individually via /review-bugbot and /review-security respectively. This preemptive scanning helps catch errors prior to code submission.

The /review command also integrates with GitHub and GitLab. If a pull request contains the same code diff as a prior /review run, Bugbot will recognize it, skip the redundant analysis, and note the existing review. This functionality is available in Cursor 3.7+ and on cursor.com/agents, with CLI support expected soon.

Focus Reviews on New Code

Bugbot previously re-analyzed entire pull requests with each update, which could lead to flagged issues in previously approved code. The updated system can now be configured to analyze only new changes since the last review, ensuring feedback remains focused on recent modifications.

This targeted approach streamlines the Bugbot code review process.

Under the Hood: Composer 2.5

These performance gains are attributed to underlying harness improvements and advancements in training Composer 2.5, the AI model now powering Bugbot. This continuous model training is central to Bugbot's ongoing development.

Organizations can manage model usage via blocklists; opting out of Composer 2.5 will cause Bugbot to default to the next best available model. Actual performance may vary based on individual configurations, similar to how other platforms like PlanetScale Taps AI for Code Review leverage AI.

The update also builds on previous enhancements, such as the introduction of Cursor Automations Go Live.

© 2026 StartupHub.ai. All rights reserved. Do not enter, scrape, copy, reproduce, or republish this article in whole or in part. Use as input to AI training, fine-tuning, retrieval-augmented generation, or any machine-learning system is prohibited without written license. Substantially-similar derivative works will be pursued to the fullest extent of applicable copyright, database, and computer-misuse laws. See our terms.

#Bugbot #Cursor #AI #Code Review #Developer Tools #Composer 2.5