BugBot Issue "Skipping BugBot: disabled for this reposiroty"

[Daniel_Stojanovic]

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Getting the error
Skipping Bugbot: Bugbot is disabled for this repository
although settings seem to be correct and bugbot enabled for the repo in question.

This bug has been reported multiple times, e.g in Bugbot is not running on newly configured repository and Skipping Bugbot: Bugbot is disabled for this repository, while running bugbot for the PR

Bugbot request id: serverGenReqId_7c416ee0-08b6-4b3d-9cef-6dfed4f20aea

Steps to Reproduce

• setting up bugbot (see screenshots)
• Commenting one of the following in an open PR:
  bugbot run
  @cursor review

Expected Behavior

BugBot should review the PR

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

opened PR using Claude Code (Opus 4.5)

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

This is a known issue. It usually happens when the same GitHub account is connected to multiple GitHub App installations or multiple Cursor subscriptions.

Could you please confirm:

1. Do you have multiple Cursor subscriptions (personal and work) connected to this GitHub account?
2. Go to Dashboard > Integrations (https://cursor.com/dashboard?tab=integrations). Do you see more than one GitHub installation?

For now, I’ll pass the request ID to our engineers so they can check the backend routing.

If you do have multiple installations, a temporary workaround is to disconnect the GitHub App from your personal subscription.

[Daniel_Stojanovic]

Hey Dean,
thanks for the quick reply! just one GH installation as far as I can tell. Not sure about the subscription part: I only have one subscription, but there are colleagues who have subscriptions as well that might be connected with this GH org. Is that what you mean? Should they uninstall the Cursor app on their end?

Cheers

[deanrie]

Hey, it looks like the issue is a routing error on our side. When teammates in the same GitHub org have separate Cursor subscriptions, requests can sometimes get routed to the wrong installation.

Temporary workaround:
Ask teammates who aren’t using BugBot to disable their GitHub app in Dashboard > Integrations. This should route all requests through your installation where BugBot is enabled.

The team is aware and is working on a fix. Let me know if this helps.

[MikkelDB (Mikkel B)]

Is there an ETA on a fix @deanrie?

I would be nice not having to juggle permissions for this and it has been an issue since October.