Bugbot charges you again every time you push. We don't.

Bugbot no longer has a seat fee. Cursor retired the $40 per seat per month Bugbot subscription in May 2026, and the change landed for existing customers at their first billing renewal after 8 June 2026. Bugbot is now billed purely on usage: Individual plans draw it from included usage, Teams bills it from on-demand spend. Cursor publishes an average of $1.00 to $1.50 per Bugbot run depending on PR size and complexity, and Cursor staff have confirmed on the Cursor forum that this figure is per run rather than per pull request. Bugbot itself is not sold standalone, so you also need a Cursor plan: Pro from $20/mo, or Teams at $40/user/mo.

Bugbot runs an automatic review on every PR update by default, and each run is billed. Incremental Review, which is on by default, narrows each pass to the changes since Bugbot last looked, but it does not stop that pass from being charged. Teams on the Cursor forum report 7 to 10 runs on a single iterative pull request, and one thread describes 28 review rounds on one branch. That is why the honest unit for budgeting is runs per month, not PRs per month.

It depends on how much your team pushes. Optibot is flat: Plus is $29/user/mo and Pro is $49/user/mo on annual billing, with no per-review or per-file charge. Bugbot has no seat fee, so a developer who opens a few tightly scoped PRs a month and merges them without much iteration can come in under $29 of runs. Once a developer averages more than about 24 billed runs a month at $1.20 each, the flat seat is the cheaper line item, and unlike usage billing it does not move. Use the calculator on this page with your own team size, PR cadence and runs per PR rather than taking either headline number at face value.

Yes. Bugbot supports GitHub (including GitHub Enterprise Server), GitLab (including GitLab Self-Hosted), Bitbucket (including Bitbucket Data Center) and Azure DevOps in limited availability. It also does not require the Cursor editor: Bugbot connects to your repositories and reviews pull requests independently of what your engineers code in. Optibot supports GitHub and GitLab, cloud and self-hosted, with Bitbucket and Azure DevOps in development.

Bugbot reads more than the raw diff: Cursor describes it as finding issues in how a change interacts with existing components, not only in the touched lines. But its default review scope is incremental, meaning each run looks at the changes since Bugbot last reviewed, and reviewing the full pull request diff on every push is an opt-in setting. Optibot indexes your entire repository on every push and reasons over that codegraph on every review, which is what catches cross-file and architectural regressions that a change-scoped pass can miss.

Not in the sense of an engineering productivity platform. Cursor Teams provides Bugbot review analytics: findings per review, billed cost, resolution status, severity, and per-rule acceptance rates. Those measure the reviewer. They do not give you PR cycle time, review turnaround, deployment frequency, AI code ratio or contributor productivity. Optibot Pro includes those in the same seat, so the review tool and the measurement of whether reviews are actually speeding you up are one product rather than two.

Every hard claim about Bugbot comes from Cursor's own published material: the May 2026 pricing blog post for the retirement of the $40 seat and the $1.00 to $1.50 per-run average, the Bugbot documentation for platform support, review triggers, Incremental Review and effort levels, and the Cursor pricing page for plan prices. The per-run rather than per-PR reading, and the Teams-only scope of effort levels, are both from a Cursor staff reply on the Cursor forum. Reviewer commentary is quoted from public Cursor forum threads and linked to the original. Verify current pricing on Cursor's site before making a decision.