$ git diff main -- tool/cursor-bugbot.md
commit a1b2c3d - author: Oliver Wakefield-Smith - verified 22 Sep 2026
Cursor BugBot: Usage-based on a Cursor plan, with no published BugBot ratesrc. Usage-based, with no seat fee for BugBot. Individuals draw on the usage included in a paid Cursor plan; Teams bill BugBot from on-demand spend. Deployment: saas. Platforms: github, gitlab, bitbucket, azure-devops. No BYOK. The $40 seat is retired. BugBot now bills from usage, with no published rate of its own.
@@ pricing facts @@verified 2026-09-22
1+Cheapest published: Usage-based on a Cursor plan, with no published BugBot ratesrc
2+Model: Usage-based, with no seat fee for BugBot. Individuals draw on the usage included in a paid Cursor plan; Teams bill BugBot from on-demand spend
3+Free tier: None for BugBot. It is listed on the paid Pro ($20/mo), Pro+ ($60/mo) and Ultra ($200/mo) plans, not on the free Hobby plan
4+Enterprise: Cursor Teams $40/user/mo or Enterprise: contact sales. BugBot spend sits on top of the seat
@@ deployment + platform coverage @@hard constraints
1Deployments: SaaS
2Git platforms: github, gitlab, bitbucket, azure-devops
3-BYOK: no - vendor owns the model bill
@@ verdict @@opinion
1A genuine PR reviewer on all four Git platforms, attached to a Cursor plan you are probably already paying for. The catch is that you cannot budget it from the rate card: Cursor publishes plan prices and an average run cost, not a BugBot price, so the only way to size the bill is to run it and watch the meter.
@@ buyer fit @@who this is for
1+Teams already paying for Cursor, where BugBot is spend on an existing account rather than a new vendor
2+Spiky PR volume, where usage billing beats paying for idle seats
3+Shops on GitLab, Bitbucket or Azure DevOps that assumed BugBot was GitHub-only
@@ watch out @@what to verify
1-No published per-seat or per-review rate. Cursor quotes an average run cost of $1.00 to $1.50, which is an average, not a price
2-Usage billing means the cost of a review-everything policy is unbounded until you cap it
3-Existing seat-plan customers only moved across at their first renewal after 8 June 2026, so an older quote may still show $40
4-The old framing of this as an IDE bug-finder was wrong. It reviews pull requests and posts comments, competing directly with CodeRabbit and Greptile
@@ recent changes @@git log
1
commit aabbcc1-OWS-2026-09-22
Re-verified Cursor BugBot pricing
Cursor retired the BugBot seat SKU. Its 11 May 2026 post says BugBot is switching from a $40 per seat per month subscription to usage-based billing for Teams and Individual plans, taking effect at each customer's first renewal after 8 June 2026. Cursor now publishes no per-seat BugBot rate: the plan cards read 'Bugbot on usage-based billing' and the docs say BugBot Teams bills from on-demand spend. The $40 still on the rate card is the Cursor Teams seat, and the plan is Teams, not Business. Our previous $40 add-on plus $40 Business prereq described a product that no longer exists.
@@ footnote @@aux
1BugBot is a pull request reviewer, not the IDE bug-finder we previously described: Cursor's docs say it analyzes PR diffs and leaves comments with explanations and fix suggestions, and publishes a CI status for each run. Connected providers are GitHub including Enterprise Server, GitLab including self-hosted, Bitbucket including Data Center, and Azure DevOps Services. Cursor publishes an average run cost of $1.00 to $1.50 depending on PR size and complexity, which is an average rather than a rate, so no $/PR figure is carried here. Teams still on the old seat plan can read the retired terms on Cursor's legacy BugBot pricing page.
@@ cross-links @@related
1/vs/cursor-bugbot-vs-coderabbit - Cursor BugBot vs CodeRabbit
2/thread/cursor-bugbot-add-on - Seat SKU retired, May 2026
3/calculator - model your team
4/scorecard - all 19 ranked