A PR was opened by a GitHub App bot account (author_association: NONE). The Cursor Agent Review (cursor[bot]) ran automatically and posted an APPROVED review, but its body stated: “Cursor Bugbot was not present on this PR after polling, so that signal was skipped.” Manual bugbot run comments were acknowledged with a server-generated request ID, but no Bugbot review was ever posted — no inline comments, no check run, no status update. The request appears to have been queued but never executed.
Steps to Reproduce
Open a PR authored by a GitHub App bot account (not a human user)
Observe that the Cursor Agent Review runs but reports Bugbot was not present
Comment bugbot run on the PR
Bugbot returns a request ID (e.g. serverGenReqId_4596bd29-14c2-4d72-bf5f-9667737da1b5) but no review is ever posted
Expected Behavior
Bugbot should run a review and post findings (or a clean check) when triggered via bugbot run comment, regardless of PR author type. The docs state “Bugbot runs for all contributors to enabled repositories.”
Short answer: yes, this is expected on a personal (individual) Bugbot install. On an individual install Bugbot only reviews PRs you author, so a PR opened by a GitHub App bot account gets skipped, and there’s no per-user setting to change that on an individual install. That’s also why your own PRs review fine but ones opened by another account (human or bot) don’t.
The docs draw this line explicitly:
Individual: “Bugbot runs only on PRs you author.”
Team: “Bugbot runs for all contributors to enabled repositories, regardless of team membership.”
So to have Bugbot review PRs from all contributors (including a bot account), you’d want a team-owned install: a team enables the repo, billing draws from the team rather than the PR author, and you can set allow/deny lists for reviewer logins so the bot’s login is covered. Details here: Bugbot | Cursor Docs
The one thing that genuinely isn’t ideal is that bugbot run returned a request ID but posted nothing explaining the skip. That silent skip is a rough edge we’ve seen come up before, so you’re not doing anything wrong; I’ve passed your report along so we can look at surfacing a clear “skipped because…” message instead of staying quiet.
Following up on this one. Since you posted, we’ve changed how Bugbot handles this case: when a manual bugbot run can’t review a PR because the PR author doesn’t match the account Bugbot is billed to, it should now leave a comment on the PR explaining why, instead of going quiet after the request ID.
Automatic runs still skip quietly in that situation, and the team-owned install route described earlier in this thread is still the way to get PRs from other accounts (including bot accounts) reviewed.
If you’re still seeing a manual bugbot run return a request ID with nothing after it, please open a new thread with updated details and we’ll take a look!
Im on an individual account and i have setup bugbot under the “Automations” page, which would indicated that bugbot can run in those automations, but because i have a individual account bugbot wont run when the cloud agent in the automation creates the PR?
Do you not see how ridiculous and confusing this it???
Hey @Jonathan5, sorry for the confusion, the earlier answer in this thread was about PRs opened by a third-party GitHub App bot, which is a different case from yours.
On an individual plan, Bugbot does review PRs opened by a Cursor cloud agent that you started, and that includes agents launched from your Automations. Looking at your account, Bugbot reviewed a PR opened by one of your cloud agents this morning and left inline comments on it.
The PRs from last week that didn’t get a review were skipped because Bugbot itself wasn’t switched on for your account until Sep 23. Automatic runs skip quietly in that situation instead of commenting on every PR. Anything opened since then should be getting reviewed.
If you find a PR opened after Sep 23 that Bugbot didn’t review, could you open a new thread with the PR link? We’ll take a look.