Cursor
Cursor Bugbot
Cursor Bugbot is a Cursor pull-request reviewer on GitHub, GitLab, Bitbucket, Azure DevOps (limited), billed as usage-based, last verified August 16, 2026. Cursor’s production reviewer: bug-first, not style-first, and wired back into the Cursor editor the team already switched to.
Catalog record checked August 16, 2026; vendor pricing and policies can change.
| Specification | Cursor Bugbot |
|---|---|
| Vendor | Cursor |
| Git hosts | GitHub, GitLab, Bitbucket, Azure DevOps (limited) |
| Surface | PR check plus Cursor editor fixes |
| Billing model | Usage-based |
| Hourly / throughput | Usage-based; API 30–60 req/min |
| Trial | 14-day free trial on all plans (product page). |
| Config / rules | .cursor/BUGBOT.md; team/repo rules (30k chars each, 100k combined per review) |
| Inline comment cap | Not verified |
| Self-hosted option | No |
| CI hosts | Not a separate CI product |
| Autofix | Yes |
| Merge gate | Yes |
| Free for qualifying OSS | Not verified |
How a review works. Automatic review on each PR update, or comment cursor review / bugbot run. Reads existing PR comments as context. Default check conclusion for findings is neutral — requiring the Cursor Bugbot check alone does not block merge; fail-on-unresolved-issues must be enabled. Autofix can land in the Cursor editor or via Background Agent. Effort levels (Default / High / Custom) are usage-based-plan only.
Pricing (verified). Usage-based since the May 2026 change (legacy $40/seat plans renew onto usage billing after 2026-06-08). Individuals consume included usage then on-demand; Teams bill from on-demand spend. Cursor Pro ($20/mo) lists Bugbot on usage-based billing; Teams ($40/user/mo) lists agentic code reviews with Bugbot. Cursor’s May 2026 blog: average run $1.00–$1.50 depending on PR size — that is a vendor average, not a published per-run list price. Confirm live rates at cursor.com/pricing#bugbot. 14-day free trial on the product page.
Hourly / throughput. No published hourly PR-review cap. Bugbot API: most endpoints 60 requests/minute per team; POST /bugbot/review 30/minute; dry-run 10/minute. Reviews first consume included usage (Individuals) or on-demand spend (Teams). Autofix uses Cloud Agent credits at plan rates. Higher effort levels cost more usage.
Trial. 14-day free trial on all plans (product page).
Watch out. Not a substitute for choosing Cursor the editor — that comparison lives under /ai-harnesses. Usage billing means a busy repo can outrun a flat-seat mental model; size spend from cursor.com/pricing#bugbot, not from a third-party $/run table. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted.
Compare Cursor Bugbot
Common questions
Questions about Cursor Bugbot
Answered from the verified figures on this page rather than general guidance.
What is Cursor Bugbot?
Cursor’s production reviewer: bug-first, not style-first, and wired back into the Cursor editor the team already switched to. It reviews on GitHub, GitLab, Bitbucket, Azure DevOps (limited) as pr check plus cursor editor fixes.
How does Cursor Bugbot price reviews?
Usage-based since the May 2026 change (legacy $40/seat plans renew onto usage billing after 2026-06-08). Individuals consume included usage then on-demand; Teams bill from on-demand spend. Cursor Pro ($20/mo) lists Bugbot on usage-based billing; Teams ($40/user/mo) lists agentic code reviews with Bugbot. Cursor’s May 2026 blog: average run $1.00–$1.50 depending on PR size — that is a vendor average, not a published per-run list price. Confirm live rates at cursor.com/pricing#bugbot. 14-day free trial on the product page.
What is the hourly or throughput limit for Cursor Bugbot?
No published hourly PR-review cap. Bugbot API: most endpoints 60 requests/minute per team; POST /bugbot/review 30/minute; dry-run 10/minute. Reviews first consume included usage (Individuals) or on-demand spend (Teams). Autofix uses Cloud Agent credits at plan rates. Higher effort levels cost more usage.
Is there a trial for Cursor Bugbot?
14-day free trial on all plans (product page).
Does Cursor Bugbot autofix or block merges?
Autofix: Yes. Merge gate: Yes. Automatic review on each PR update, or comment cursor review / bugbot run. Reads existing PR comments as context. Default check conclusion for findings is neutral — requiring the Cursor Bugbot check alone does not block merge; fail-on-unresolved-issues must be enabled. Autofix can land in the Cursor editor or via Background Agent. Effort levels (Default / High / Custom) are usage-based-plan only.
What is the catch with Cursor Bugbot?
Not a substitute for choosing Cursor the editor — that comparison lives under /ai-harnesses. Usage billing means a busy repo can outrun a flat-seat mental model; size spend from cursor.com/pricing#bugbot, not from a third-party $/run table. Requiring the Bugbot check without fail-on-unresolved-issues still allows merge when findings are posted.