We are reviewing our Cursor licensing and would like to better understand the relationship between Team seats and Bugbot availability.
Cursor documentation indicates that Bugbot now uses usage-based billing. However, we could not find documentation that clearly explains whether Bugbot functionality depends on active Team seats or if it operates independently once repository integrations are configured.
Questions
Does Bugbot require a minimum number of active Team seats to remain operational?
Can Bugbot continue reviewing merge requests/pull requests as long as the repository integration remains configured and billing is active?
Is Bugbot availability tied to Team membership, or is it primarily governed by repository integration and usage-based billing?
Reason for Request
We would like to understand the operational and licensing requirements for Bugbot beyond the usage-based pricing information currently available in the documentation.
Hi @Neha_Kapila Great questions! Let me take a pass at each one:
Bugbot no longer has its own per-seat fee. Runs are billed from your team’s usage. However, Bugbot still operates within an active Cursor Team, so a few requirements remain.
1. Does Bugbot need a minimum number of active Team seats?
There’s no dedicated “Bugbot seat” count anymore, but on a Team plan Bugbot does require at least one active, paid Team member. If a team is left with zero paid seats, Bugbot stops running until a paid seat is restored.
2. Can Bugbot keep reviewing PRs/MRs as long as the integration is configured and billing is active?
Yes! Note that if you hit your spend limit, Bugbot will pause until the limit is increased or the next cycle rolls around.
3. Is availability tied to Team membership, or to repo integration + usage-based billing?
Primarily team membership. You can also run bugbot on an individual plan but it’s not designed for collaboration. You get more features and control with Bugbot for teams.
Oh @alorbach, then note that recently there was a bug affecting how the models are displayed inside the dashboard page, because like, this was supposed to be a Fable call, but because it used the auto review mode (that calls gpt 5.4 mini on the background -does not charge the user-) it resulted in the model being wrongly displayed, I will check with the team to see if those two issue are linked or not! Good catch tho
Can a single paid Team seat support Bugbot reviews across all connected repositories in the Team workspace, regardless of the number of developers contributing to those repositories?
If Team seat counts are reduced significantly, does Bugbot functionality, access controls, repository integrations, or billing behavior change in any way, provided at least one paid Team seat remains active?
Yes, a single active paid Team seat can keep Bugbot available across the Team’s enabled repositories. Bugbot Teams is usage-based, so reviews are billed from on-demand spend per review rather than per developer or per Bugbot seat.
For automatic reviews, once Bugbot is enabled on a repository and configured to run automatically, it can review PRs from all contributors to that repository, regardless of whether each contributor is a Cursor Team member.
The main nuance is around who can start reviews manually. Comment-based manual triggers such as bugbot run or cursor review are controlled by Team membership and your Bugbot access settings. Running Bugbot from inside Cursor requires the person using Cursor to have access to the IDE through their own paid seat.
If you reduce Team seats but keep at least one active paid Team seat, Bugbot’s automatic review behavior, repository integrations, access controls, and usage-based billing do not change just because the seat count changed. The repositories still need to remain connected and enabled, Bugbot needs to remain on, and on-demand spend needs to be available. If your spend limit is reached, Bugbot pauses until the limit is raised or the next cycle starts.
The key requirement is that the Team remains an active paid Team. If the Team drops to zero paid seats, Bugbot stops until a paid seat is restored.
