Guide
Cursor Bugbot Review Guide
Answer first
Cursor's June 2026 Bugbot update says average review time is about 90 seconds, down from about 5 minutes; Bugbot finds 10% more bugs per review, costs about 22% less per run and is powered by Composer 2.5.
What changed in Cursor Bugbot, June 2026?
Cursor's June 2026 BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. update says average review time is about 90 seconds, down from about 5 minutes; Bugbot finds 10% more bugs per review, costs about 22% less per run and is powered by Composer 2.5.
- Release fact
- Speed
- Why it matters
- Average BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. review time is about 90 seconds, down from about five minutes.
- Release fact
- Quality
- Why it matters
- Cursor reports 0.62 bugs per review on average, up from 0.56.
- Release fact
- Cost
- Why it matters
- Cursor reports about 22% lower cost per run.
- Release fact
- Composer 2.5
- Why it matters
- The June improvement is tied to Composer 2.5 powering BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs..
- Release fact
- /review
- Why it matters
- Developers can run
/review,/review-bugbotor/review-securitybefore pushing.
- Release fact
- Incremental review
- Why it matters
- BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. can review only what changed since the last review.
| Release fact | Why it matters |
|---|---|
| Speed | Average BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. review time is about 90 seconds, down from about five minutes. |
| Quality | Cursor reports 0.62 bugs per review on average, up from 0.56. |
| Cost | Cursor reports about 22% lower cost per run. |
| Composer 2.5 | The June improvement is tied to Composer 2.5 powering BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs.. |
| /review | Developers can run /review, /review-bugbot or /review-security before pushing. |
| Incremental review | BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. can review only what changed since the last review. |
Release facts checked on 2026-06-23. Use the linked Cursor sources before quoting product mechanics in a live customer, security or pricing conversation.
How should a team use Cursor Bugbot review?
- 1Run BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. on real PR diffs, not as a replacement for tests or code owners.
- 2Use
/reviewlocally before push when a change is risky or security-sensitive. - 3Configure model blocklists, effort and incremental review so findings match team risk.
- 4Treat findings as review evidence; humans still decide what merges.
Interactive diagram. Use Tab to move through hotspots or use the step controls when shown.
What should stay bounded?
Do not call a clean BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. run merge approval.
Tune noisy findings with repo rules and effort levels instead of ignoring the tool.
Keep pricing and effort assumptions fresh because BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. billing and usage can change by plan.
Frequently asked questions
Who is Cursor Bugbot Review Guide for?
Engineers, code reviewers and DevEx teams adding Bugbot to local and pull-request review workflows.
What makes this page credible?
The guide cites Cursor's June 10, 2026 Bugbot changelog and May 2026 billing update, with current metrics separated from older claims.
What should I do next?
Start with one real repo task, capture the prompt and review the result before scaling the workflow.
Editorial notes
Source review
- Last checked
- June 23, 2026
- Scope
- Cursor docs, Cursor Learn pages and product docs.
- Refresh
- Quarterly, plus changes to Cursor agent or CLI docs.
- Reviewer
- Learn Cursor editorial
Page assets
- Primary media
- Workflow diagram.
- Supporting media
- Learn Cursor practice screenshot.
- Interactive element
- Step diagram.
- Transcript
- Add a transcript when a recorded walkthrough is added.
- Refresh owner
- Learn Cursor editorial.
Content pod
- Pod
- Workflow pod
- Owner
- Editorial director
- Reviewers
- DevRel engineer, SEO lead, Senior editor
QA gate
- Human signal
- Includes a task-specific diagram, checklist or calculator.
- Claims
- Claims stay tied to sources, visible limits and page scope.
- Visual proof
- Uses product screenshots or annotated workflow diagrams, not stock art.
- Page rhythm
- Sections vary between answer, method, visual and action blocks.
Sources & last verified
- Cursor changelog: Bugbot June 2026 update
- Cursor blog: Updates to Bugbot for Teams and Individuals
- Cursor changelog
Cursor ships frequently. Facts verified against primary sources on June 23, 2026.