Short answer: Cursor’s billing guide reports an average Bugbot run cost of $1.00–$1.50, depending on pull-request size and complexity. It is an average, not a guaranteed per-review rate. Individuals use included usage first, then on-demand usage if enabled; Teams reviews are charged from on-demand usage.
What does Bugbot cost, and which plan includes it?
Cursor’s plan documentation lists Bugbot on Premium and higher subscription tiers; Plus does not include it. Premium is listed at $30/month or $300/year. These are Cursor subscription prices—not a fixed Bugbot review fee. Bugbot usage may add charges depending on the billing path and reviews run.
The reviewed materials do not establish whether a customer can buy Bugbot on its own or must have a paid Cursor subscription for the applicable purchase path. Confirm that requirement for your account before treating the Premium subscription price as a minimum total cost. For Teams, the reviewed pricing information does not establish the applicable seat price, so check the current plan and billing details rather than relying on an estimate here.
Cursor’s billing guide says usage-based Bugbot billing is available immediately to new customers. For existing Bugbot customers, the change applies at their next billing renewal after June 8, 2026; their current Bugbot billing remains in place until then.
The old seat-based prices are historical, not the current usage rate: Cursor’s legacy pricing page lists $40/month for an individual Bugbot subscription and $40 per user/month for Teams, and labels them pre-May-2026 pricing.
How included usage and additional billing work
- Individual plans: Bugbot uses included usage first. After that usage is consumed, it bills on-demand if on-demand usage is enabled. If it is disabled, Bugbot pauses until the next billing cycle, when limits reset.
- Teams: Bugbot reviews are charged from on-demand usage. A Cursor staff reply says the on-demand spend cap is shared across chat and Bugbot, not reserved for Bugbot alone.
There is a plan-allowance detail the reviewed material does not resolve: Bugbot’s help page says some Individual and Teams plans include monthly usage, but does not name the plans or state the quantities. Do not assume a particular allowance or that it offsets a Teams on-demand charge without checking the billing details for your account.
Estimating Bugbot spend
Cursor’s reported $1.00–$1.50 per run is a rough benchmark, not a fixed rate. Cursor also reported that a June 2026 update made Bugbot runs about 22% cheaper, but did not give a replacement average; that percentage alone is not enough to calculate a guaranteed current price.
For a practical budget, use your own billed-review data:
Projected review usage value = expected reviews × your observed average billed cost per review
Illustration, not a Cursor quote: If 40 reviews produced $44 in billed usage, your observed average would be $1.10 per review. At 100 similar reviews, projected review usage value would be 100 × $1.10 = $110. That is not necessarily the additional amount due: an Individual account may consume included usage first, while Teams reviews are charged to on-demand usage. Cursor’s Teams Analytics API can return billed cost for completed Bugbot reviews, which can help teams calculate an account-specific average.
Count reviews, not just pull requests: Cursor’s Bugbot reference says repeat reviews of the same PR count as usage, while a run skipped because the PR is too large records no review usage.
Does using a production model API key change Bugbot’s cost?
The reviewed documentation does not establish that Bugbot can be routed through a customer-provided production model API key or endpoint, or that doing so changes its charges. Cursor’s API-key documentation says custom API keys work with chat models; it does not document a Bugbot configuration. Do not subtract external API credits from a Bugbot budget based on general Cursor API-key support.
Budget takeaway: Treat $1–$1.50 per run as Cursor’s reported average, not a fixed rate. Add a Cursor subscription cost only if the applicable purchase path requires one; account for whether your plan uses included or on-demand Bugbot usage, and estimate future spend from your own billed reviews. The reviewed materials do not establish named-plan monthly allowances or whether Bugbot can be purchased standalone.
Sources
Bugbot usage-based billing — Cursor Docs
Pricing and plans — Cursor Docs
Legacy Bugbot pricing — Cursor Docs
How to turn on-demand usage just for Bugbot? — Cursor Community Forum
Bugbot June 2026 update — Cursor