Bugbot disabled for repository even though GitHub App is installed and Bugbot is Active

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

I’m on Cursor Pro Individual and I’m trying to enable Bugbot for a private GitHub repository.

Repository:
igor-yek/retailserv-platform

What works:

  • GitHub repository is private and exists.
  • Cursor GitHub App is installed.
  • The GitHub App has access to the repository.
  • I tried both selected repository access and all repositories access.
  • Bugbot is shown as Active in Cursor Dashboard.
  • Pull Request exists and was authored by the same GitHub account.
  • Commenting bugbot run in the PR reaches Cursor Bot.

Problem:
The PR receives this response:

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

In Cursor Dashboard → Bugbot, the repository list shows:
igor-yek / GitHub — 0/1 Repositories Enabled

But the Enable button does not respond. The top loading spinner keeps spinning indefinitely.

I tried:

  • Chrome normal mode
  • Chrome Incognito
  • Microsoft Edge
  • Ctrl+F5
  • waiting several minutes
  • GitHub App access set to selected repository
  • GitHub App access temporarily set to all repositories

The result is the same.

Verbose request IDs:

  • serverGenReqId_6dde8e83-91af-467f-9e35-6c564a7eff79
  • serverGenReqId_e0f2a3b2-0518-4024-ab39-152de22596b0

Steps to Reproduce

  1. Create or open a private GitHub repository.
  2. Install and authorize Cursor GitHub App.
  3. Grant Cursor access to the repository.
  4. Open Cursor Dashboard → Bugbot.
  5. Enable Bugbot globally. Bugbot shows as Active.
  6. Try to enable the repository under Repositories.
  7. Observe that it shows 0/1 Repositories Enabled.
  8. Click Enable.
  9. The button does not respond and the top loading spinner keeps spinning.
  10. Open a Pull Request in the repository.
  11. Comment bugbot run.
  12. Cursor Bot replies: “Skipping Bugbot: Bugbot is disabled for this repository.”
  13. Comment bugbot run verbose=true.
  14. Cursor Bot returns a request id, but no Bugbot review appears.

Expected Behavior

The repository should be enabled for Bugbot from the dashboard, changing from 0/1 to 1/1 enabled.

After commenting bugbot run on a Pull Request, Bugbot should review the PR or show a clear actionable error explaining why it cannot run.

Screenshots / Screen Recordings

Снимок экрана 2026-06-14 224017.png
Снимок экрана 2026-06-14 224017.png1802×800 34.3 KB

Operating System

Windows 10/11

Version Information

Cursor version: 3.7.36 (user setup)
VS Code Extension API: 1.105.1
Build type: Stable
Release track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Bugbot / Cursor Bot on GitHub Pull Request.
No chat model selected manually.

For AI issues: add Request ID with privacy disabled

serverGenReqId_6dde8e83-91af-467f-9e35-6c564a7eff79
serverGenReqId_e0f2a3b2-0518-4024-ab39-152de22596b0

Additional Information

The GitHub App can see the repository and Cursor Bot responds in the PR, so the GitHub connection appears to work. The issue seems to be specifically in the Cursor Dashboard Bugbot repository enable step.

The dashboard shows Bugbot as Active, but the repository remains at 0/1 Repositories Enabled. The Enable button does not respond, and the top loading spinner keeps spinning indefinitely.

I also tried setting GitHub App access to All repositories, but the PR still receives: “Skipping Bugbot: Bugbot is disabled for this repository.”

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The request IDs and screenshot really helped.

This is a known bug with enabling a repo in the Bugbot dashboard, not an issue on your side. The fact that the GitHub App can see the repo and bugbot run reaches Cursor Bot confirms the connection is working correctly. The “0/1 Repositories Enabled” state is stuck on our side. The Enable button can’t overwrite it, so the PR ends up with “disabled for this repository”. As an individual Pro user, you don’t need team admin permissions for this. It’s not a permissions issue.

I’ve reported this internally with your details. This case needs a manual relink/enable on our side. The dashboard can’t fix this stuck state, so incognito, reconnect, or all-repos won’t help here. You’ve already tried all that.

7

Thanks for confirming.

Please proceed with the manual relink/enable for the repository:

igor-yek/retailserv-platform

I will keep the GitHub App access unchanged and leave the test PR open for diagnostics.

Once the manual enable is done, I’ll refresh the Bugbot dashboard and run “bugbot run” again in the PR.

10

Thanks, Igor. Noted, and thanks for keeping the test PR open.

To set expectations honestly: there isn’t a self-serve path or a support-side toggle to force the repo enabled while it’s stuck in this state. It needs a fix from our engineering team, who already have your repo and account details and are tracking this alongside the other reports of the same issue. I don’t have a timeline to share, and I don’t want to over-promise a quick manual flip.

I’ll update this thread if there’s any progress on our end. There’s nothing further you need to do on GitHub in the meantime.