I have a private repo in github to which cursor and bugbot has access. In the past my current Cursor sub (Pro) allowed me three bugbot scans each month and these did automatically trigger. The last pull request 2 months ago did trigger the bugbot report. I am not aware of any change in the past 2 months that would explain why my new pull request is not being picked up by bugbot. Tried the following comment in github for the pull request: ‘cursor review verbose=true’ but got a comment in return : Bugbot request id: serverGenReqId_e41555…70ea986 after which I disconnected and reconnected my github account with cursor to no avail.
Steps to Reproduce
Create a new pull request on an existing private github repository that was triggering bugbot scans before.
Expected Behavior
A bugbot report
Operating System
MacOS
Version Information
Updated cursor to the latest version just now but should be irrelevant since I am using IntelliJ to do repo changes, commits, pushes, etc.
Hey, thanks for the report. A few things to check:
Who is the PR author? On the Individual Pro plan, BugBot only reviews PRs where the author is the same GitHub account linked to your Cursor subscription. If the PR was created by another user (or different GitHub account), BugBot will quietly skip it without explanation. This is the most common cause of these issues.
Full Request ID - you shared a truncated one (serverGenReqId_e41555…70ea986). Can you send the full one? With it, we can check the exact reason for the rejection.
Since you’re the only author and all repos are included in the dashboard, this isn’t a standard case.
A couple of things you can check for now, just in case:
In GitHub: Settings > Applications > Installed GitHub Apps, make sure only one Cursor integration is installed. If there are duplicates, delete them all and reinstall a single one.
Try creating a brand-new PR, not pushing to an existing one, and post @cursor review as a top-level comment, not a reply to another comment.
We’ll post here as soon as I have the results of the check for the Request ID.
two Github applications present: 1 x Cursor & 1x Sonar
created a new branch and a fresh pull request
same result: Bugbot request id: serverGenReqId_fd6186fa-6e3f-4275-8a4b-08ba3fdb0b90
(had to also use verbose=true to get a reply on the top-level comment)
Following up on Deanrie’s earlier reply, I checked the request IDs you provided.
The webhooks were received successfully and your GitHub account is properly linked. However, I can see that BugBot is currently not enabled at the plan level on your account. This is separate from having your repositories selected in the dashboard — there’s also a master toggle for BugBot itself.
Could you go to cursor.com/dashboard?tab=bugbot and check if BugBot is showing as enabled? If it’s off, toggle it on, then try creating a fresh PR and posting @cursor review again.
It’s possible that disconnecting and reconnecting your GitHub account may have reset this setting. Let us know if it resolves the issue.
Only Run When Mentioned
Only run when “bugbot run” or “@cursor review” is commented on a PR
Only Run Once Automatically
Automatically review when a PR is published, ignoring new pushes
Tried @cursor review verbose=true as a comment to the existing pull request
reply: Bugbot request id: serverGenReqId_ceec2874-338b-4c26-9723-a1009a61cff9
Then merged the pull request and created a new one, which should automatically trigger the review, but here also nothing is triggered/reviewed.
Thanks for confirming those settings. The two toggles you mentioned (“Only Run When Mentioned” and “Only Run Once Automatically”) control how BugBot behaves on your PRs, but there’s a separate setting that controls whether BugBot is actually activated on your Pro plan.
Right now, BugBot is not active at the plan level on your account, which means it’s falling back to the free tier (which has a limited number of runs that you’ve already used up). That’s why nothing happens even though the webhooks are coming through fine.
On the BugBot dashboard, look for an option to add or enable the BugBot license/plan — it should be separate from the behavior preferences you already configured. Once that’s active, your Pro plan’s BugBot quota should apply and reviews will start working again.
That’s the one — the Bugbot Pro License section you see under Integrations, with the Upgrade button. Your dashboard currently shows “Bugbot Free” at the top, which means BugBot isn’t activated at the plan level. The behavior toggles you enabled (Only Run When Mentioned, Only Run Once Automatically) control how BugBot runs, but they require an active BugBot license to work.
Click the Upgrade button next to “Bugbot Pro License” to start the 14-day free trial, and your reviews should start working again on the next PR.
The Cursor Pro plan allows for 3 reviews each month, correct? How do I enable that license? Your instructions to enable via Upgrade are clear, but it also starts a two week free trial of the Bugbot Pro 40 dollar/month sub, which is not what I want. What happens when I remove the license after two weeks before the monthly fee kicks in?
BugBot’s free tier included with Cursor Pro gives you a limited number of reviews total, not per month. Looks like that limit has already been used up, so new requests aren’t going through.
BugBot Pro ($40/month) is a separate add-on. The Upgrade button starts a 14-day free trial. If you decide you don’t need it, you can cancel before the trial ends and you won’t be charged. To do that: cursor.com/dashboard > Manage Subscription > Cancel subscription. You’ll keep access until the trial ends.
Free tier
On Teams and Individual Cursor plans, every user gets a limited number of free PR reviews each month. For teams, each team member gets their own free reviews. When you reach the limit, reviews pause until your next billing cycle.”
