Bug bot is enabled for my repo but not running on PR

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Bugbot is enabled for my repo and I have also given access to the repo but still I keep getting same reply.

Skipping Bugbot: Bugbot is disabled for this repository. Visit the Bugbot dashboard to update your settings.

Sharing a request ID for your ref.
Bugbot request id: serverGenReqId_da49e6e1-1230-4a01-85a1-9b7d6060810d

Steps to Reproduce

Raised a PR, then Connected Cursor app with Github, enabled bugbot, then commented bugbot run on PR.

Screenshots / Screen Recordings

image.png
image.png1996×478 23.1 KB

Operating System

MacOS

Version Information

Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hi @cHAuHaN-Arre,

When multiple users in the same GitHub org have connected their own Cursor accounts with the GitHub integration, the system can route the BugBot request through the wrong installation context. As a result, the backend doesn’t “see” that BugBot is enabled for the repo, even though the dashboard toggle shows it as on.

Here’s what to check:

  1. In GitHub: go to your org’s Settings > Applications > Installed GitHub Apps. Make sure there’s only one Cursor integration installed for the org. If there are duplicates, remove them all and reinstall a single one.

  2. Ask your team admin (the person who installed the GitHub App) to go to Dashboard > Integrations and verify the GitHub connection is properly set up.

  3. If any colleagues have their own personal Cursor subscriptions with a separate GitHub integration connected, ask them to disconnect it in Dashboard > Integrations — having multiple installations for the same org causes routing conflicts.

  4. After cleaning up, test with a new PR. Old PRs can get stuck due to outdated routing.

A similar issue was discussed in this thread with the same workaround steps.

Our team is aware of this routing issue. Let me know if the steps above don’t resolve it.