Bugbot not working after reinstall - disabled in all repositories

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Problem

Bugbot is disabled in all repositories despite:

  • Fresh reinstall of Cursor GitHub App
  • Repository explicitly added to Cursor permissions
  • Bugbot enabled in Cursor settings (all toggles on)
  • No branch protection rules blocking it

Steps to Reproduce

  1. Install Cursor GitHub App
  2. Enable Bugbot in settings
  3. Create PR in any repository
  4. Bugbot responds with “disabled for this repository”

Expected Behavior

It begin to appear after I’ve added one more repository to the existing Cursor installation in the organization. After that, all the existing repositories start being ignored by bugbot. Even when I mention it.

  1. repo appears in bugbot setting and it toggled on
  2. repo added to bugbot installation on GitHub
  3. bugbot mentioned in repo
  4. bugbot answers “Skipping Bugbot: Bugbot is disabled for this repository” despite it’s enabled in settings
  5. automatic action for bugbot review also disappear

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (system setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known issue with request routing in orgs.

It looks like after adding a new repo, the system started picking the wrong GitHub App installation to route requests through. This usually happens when multiple users in the org have their own Cursor subscriptions.

Can you check:

  1. Do any of your coworkers in the org have their own Cursor subscriptions (personal or work)?
  2. If yes, ask them to temporarily disable the GitHub App in Dashboard > Integrations (https://cursor.com/dashboard?tab=integrations). This should force the system to use your installation with an active BugBot.

Also, if you can:

  • Create a PR and comment bugbot run verbose=true
  • Share the request ID you get back. That’ll help the engineers verify the routing on the backend

The team is working on a fix, but the workaround above should help. Let me know if it works.

4
  1. yes, but I asked them to disconnect their github integrations so now there’s only my integration in this organization
  2. verbose ids:
    Bugbot request id: serverGenReqId_1c5cc9a6-f9f0-47f4-bdd5-a28820643e66
    Bugbot request id: serverGenReqId_a8e94905-dcb4-4aac-9a44-820d72b4e10a
1 Like
7

Great that the team disabled their integrations. That’s a good first step.

Can you try testing on a brand-new PR? Sometimes older PRs get stuck on the previous routing.

Let me know what you see with the new PR test.

8

I’ve tried a new PR, an old PR’s - all the same. Bugbot replies are simillar on all the PR’s - “Skipping Bugbot: Bugbot is disabled for this repository“. No bugbot’s action created on PR create

10

We’ve diagnosed the issue.

The main reason is that you have two Cursor accounts, and the system may route requests through the wrong GitHub App installation.

Here’s what you need to do:

  1. Check both accounts and make sure the GitHub App is installed only on the one where BugBot is active.
  2. In GitHub, go to Settings > Applications > Installed GitHub Apps and check if there are multiple Cursor installations for your org.
  3. If there are, remove all Cursor installations from GitHub before reinstalling.
  4. Then reinstall the GitHub App from the dashboard of the correct account: https://cursor.com/dashboard?tab=integrations

After reinstalling, test on a brand-new PR. Older PRs may still be using the old routing.

Let me know how it goes.

11

Absolutely, GitHub App installed on my account only.
Also, we got only one installation of Cursor in the organization App setting.
I’ve reinstalled it many times (5 times at least) with fully removal from the organization, but still no success. Getting the same message with all the possible solutions:

  • remove app from the org, add from cursor dashboard, access to restricted repos
  • remove app from the org, add from cursor dashboard, access to all the repos in org
  • validate that I’m the only one with connected cursor and GitHub authentication in Cursor dashboard

Nothing changes on this one

12

It looks like the usual workarounds aren’t working in this case.

Let me clarify one thing. You have two Cursor accounts: *****[email protected] and sem@****nds.dk. Did you disable the GitHub App on BOTH accounts, and then reinstall it only on one of them?

It’s important to check:

  1. Log in at https://cursor.com/dashboard as *****[email protected]. There should be no GitHub integration there.
  2. Log in as sem@****nds.dk. If you need BugBot on this account, the integration should be only here.

If you’ve already done this and the issue is still happening, we’ll need a backend check. I’ll pass this info to the team so they can look up your data using your request IDs directly.

13

On my gmail.com account bugbot not even exist, it’s disabled at all. It’s only persist on the nds.dk account and connected only to this account’s repos.

14

Resolved by last release.

2 Likes
15

@deanrie Having the exact same issue. Disconnected entirely from the old unused account and still can’t run bugbot. Ran verbose - here’s the output – Bugbot request id: serverGenReqId_786601ea-bc35-4d21-8f53-9f4a0d8e2f4d