Bugbot review queued but never executed on bot-authored PR

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

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

  1. Open a PR authored by a GitHub App bot account (not a human user)
  2. Observe that the Cursor Agent Review runs but reports Bugbot was not present
  3. Comment bugbot run on the PR
  4. 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.”

Operating System

MacOS

Version Information

Version: 3.11.19
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

For AI issues: add Request ID with privacy disabled

serverGenReqId_4596bd29-14c2-4d72-bf5f-9667737da1b5

Additional Information

  • Bugbot works normally on human-authored PRs in the same repo (confirmed on multiple recent PRs)
  • The repo is enabled in the Bugbot dashboard
  • The only variable that changed is the PR author being a bot account
  • Does Bugbot skip or silently fail on PRs authored by GitHub App bot accounts? If so, is there a setting to enable it?

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey there!

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.