Bugbot not running in a repo it used to work in

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Hey,
I have an active Bugbot subscription, in a lot of my PRs I’m getting: “Skipping Bugbot: Bugbot is disabled for this repository”, although it is enabled in my account.
I have two Cursor subscriptions that are connected to the same Github account. One subscription is from work and the other is my personal.
In my work subscription I have Bugbot but in the personal one I don’t, maybe it’s related to that but I’m not sure.

Please advise

Thank you in advance

Steps to Reproduce

Try to run BugBot manually or not manually

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.0-pre.23.patch.0
VSCode Version: 1.105.1
Commit: 0ddbd2e3ee5dabb796d837501e34beb6cf3038c0
Date: 2025-12-03T08:22:56.039Z
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.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

The message “Bugbot is disabled for this repository” usually means the repo isn’t included in the GitHub App/team installation that’s triggering the run.

Please check:

  • Dashboard > Integrations: that the GitHub App is installed on the correct org/repo and that the repo belongs to the active installation where Bugbot is enabled - Cursor - The AI Code Editor
  • Dashboard > Bugbot: that this specific repo is included in the active subscription - Cursor - The AI Code Editor
  • If you have two installations on the same GitHub account, make sure the PR belongs to the installation/team with Bugbot enabled, not a personal one without Bugbot - Bugbot | Cursor Docs

Let me know if you run into any trouble.

Hey Dean,

first of all thanks for the swift reply.

I’ve double checked all of the above,
the app is installed within the repo and the repo is enabled in the Cursor dashboard.

For some of my other teammates BugBot does work btw.

Got it. Since it works for your colleagues in the same repo but not for you, it’s likely tied to your account and how the system picks the active installation.

To diagnose, please:

  1. Leave a comment cursor review verbose=true on any problematic PR - this will return a request ID
  2. Share that request ID here

With the request ID, we can check on the backend why your account is being routed to the wrong installation. This looks like a routing bug when there are two subscriptions on the same GitHub account.

Let me know once you have the request ID.

serverGenReqId_306f01a2-6119-4094-85b6-2b79157fac79

1 Like

Thanks. We checked and your repositories are connected but not enabled for Bugbot.

Please:

  1. Go to Dashboard > Bugbot and enable the needed repository - Cursor - The AI Code Editor
  2. Make sure the GitHub App is installed on the right organization and has access to this repo - Cursor - The AI Code Editor
  3. Bugbot instructions - Bugbot | Cursor Docs

The dashboard says that they are connected

Thanks for the screenshot. We see that your admin panel shows “0 Enabled”, while your dashboard shows “50 Enabled”. This might be a routing bug between the two subscriptions.

Possible workarounds while we wait for the fix:

  1. Temporarily disable the personal GitHub subscription (Dashboard > Integrations > disable GitHub for your personal account)
  2. Or use different GitHub accounts for your work and personal Cursor subscriptions

I’ve passed this to the engineers to fix the routing.

Let me know if the first option helps.

Will try, thanks!

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.