Skip to content
News Product launch

Cursor BugBot now runs in 90 seconds, finds 10% more bugs, and costs 22% less

· by Pondero Newsdesk

The short version

Cursor shipped a BugBot performance update on June 10, 2026: average review time dropped from roughly 5 minutes to about 90 seconds, bug detection rate rose from 0.56 to 0.62 bugs per review, and per-run cost fell 22%. The gains come from a shift to Composer 2.5.

Cursor BugBot now runs in 90 seconds, finds 10% more bugs, and costs 22% less

Cursor published a BugBot performance update on June 10, 2026, cutting average review time from roughly five minutes to about 90 seconds while lifting bug detection and reducing per-run cost.

What

Three metrics improved at once, per Cursor's changelog. Review time fell to approximately 90 seconds from approximately five minutes, a reduction of more than 3x. Bug detection rose from 0.56 to 0.62 bugs found per review on average, a 10% gain. Per-run cost dropped 22%.

Cursor attributed the gains to Composer 2.5, the model that now powers BugBot. The company noted that speed and detection figures can vary depending on configuration and that BugBot respects model block lists.

Two workflow changes shipped alongside the performance numbers. First, developers can now run BugBot and Security Review with the /review slash command before pushing code, without waiting to open a pull request. The command accepts /review-bugbot and /review-security as direct variants. Cursor added deduplication logic so that if /review is run against a diff and a PR is later opened with the same diff, BugBot skips the redundant review and leaves a comment instead. The feature requires Cursor 3.7 or later and is available on cursor.com/agents. CLI support was listed as coming soon in the changelog.

Second, teams can now configure BugBot to review only changes added since the last review pass, rather than the full pull request each time. This setting narrows the feedback surface to the latest updates.

Why it matters

BugBot sits in the automated code-review segment, competing with tools that surface bugs and security issues in pull requests. A 90-second cycle places the tool inside a developer's active work loop rather than somewhere she checks at end of day. The 22% cost reduction matters for high-volume teams that run BugBot on every pull request across large codebases. Those two factors together change the calculus on whether to gate merges on BugBot review.

The Composer 2.5 attribution also signals direction. Cursor shipped Composer 2 last year as the model behind its agentic coding features; the 2.5 revision is now routing SDK clients that still reference the older composer-2 slug automatically, per a separate June 4 SDK changelog. BugBot's update is the first public benchmark that shows the 2.5 generation outperforming 2.0 on a production task with real detection figures attached.

What to watch next

Cursor's changelog stated CLI support for /review is "coming soon" without a date. GA of that feature would let teams wire BugBot into CI pipelines outside the IDE. The company has not published a GA date or a roadmap milestone for that change.

Sources