There are a few things to check, and some info I’ll need to dig in:
Go to the PR that was supposed to trigger BugBot and leave a comment: bugbot run verbose=true. Share the new request ID you get. This will give us more details on what’s happening.
In GitHub, go to Settings > Applications > Installed GitHub Apps and make sure only one Cursor integration is installed for your org. Sometimes a leftover install after reinstall can cause routing issues.
Hey, apologies for the slow response! I took a look at your account and can see ~30 successful BugBot runs over the last two weeks — everything looks healthy on our end. Are you still experiencing an issue?
In the backend, we can see for serverGenReqId_c8e7b0f0-9448-43e1-8a30-2e80b3b523ab:
Cannot bill pro user: the GitHub account linked to your Cursor account does not match the PR author. Please ensure you’re using the correct GitHub account.
When using an Individual plan, BugBot can only run on PRs that you authored (it matches the GitHub account linked to your Cursor account against the PR author.) If you’re each on individual Pro plans, BugBot won’t run when triggered on another person’s PR.
The team plan doesn’t have this same restriction, so you may want to consider it rather than individual plans!