Bugbot reports "disabled for this repository" despite being enabled in dashboard

[adam.michalak.dev (Adam Michalak)]

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Bugbot returns “Skipping Bugbot: Bugbot is disabled for this repository” even though the repository is visibly enabled in the Bugbot dashboard. I have followed all troubleshooting steps in the official documentation and confirmed the setup is correct.

Steps to Reproduce

Connect GitHub via the Integrations tab on cursor.com/dashboard
Enable Bugbot for the repository in the Bugbot dashboard
Open a pull request and comment “@cursor review” on any existing PR

Expected Behavior

Bugbot reviews the PR and leaves inline comments.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Latest BugBot version

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

Output of @cursor review verbose=true: “Bugbot request id: serverGenReqId_e6e01a3c-19c2-4ec0-b2c1-6f58ead178f1”

Additional Information

Troubleshooting already performed:

• Verified Bugbot is enabled for the repository in the dashboard
• Confirmed GitHub app is installed and has access to the repository
• Triggered verbose mode to obtain a request ID
• Screenshots of dashboard settings available

This issue is longstanding - it first started when my company finished Cursor trial several months ago (before it was working fine). It is reproducible in all PRs and all repositories of my organization.

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report.

This is a known routing issue. When multiple users in a GitHub org have their own Cursor accounts with the GitHub integration connected, the system can route the request through the wrong installation. As a result, BugBot “doesn’t see” that the repo is enabled.

You mentioned it started after the trial ended. It’s most likely that an old installation is conflicting with the new one.

Here’s what to check:

1. In GitHub: Settings > Applications > Installed GitHub Apps. Make sure there’s only one Cursor integration installed for your org (asiainspection). If there are duplicates, remove them all and reinstall a single one.
2. Ask your colleagues (especially anyone who might have connected Cursor earlier during the trial) to go to https://cursor.com/dashboard?tab=integrations and make sure their GitHub integration is disconnected.
3. Then test with a new PR. Old PRs may be tied to the old routing.

A similar issue is discussed here: Bugbot says “Skipping Bugbot: Bugbot is disabled for this repository”

The team is aware of this routing issue. There’s no ETA yet, but your report helps us prioritize it. Let me know if the workaround doesn’t help and I’ll pass it to engineering to check the backend.