Resolved: Can’t enable Bugbot after switching to Team plan — “Enable Bugbot” only opens GitHub connect (already connected)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

  • BugBot & Code Review

Describe the Bug

After switching to a Cursor Team plan, I can no longer enable Bugbot on any repositories. In Cursor Settings on the web (Automations), clicking Enable Bugbot only takes me to a GitHub connect screen, even though GitHub is already connected via an org install. I uninstalled and reinstalled the GitHub app and the issue persists. I cannot enable Bugbot on any orgs.

Steps to Reproduce

  1. Open Cursor Settings on the web and go to Automations.
  2. Attempt to enable Bugbot on a repository / org.
  3. Click Enable Bugbot.
  4. Observe that instead of enabling Bugbot, you are taken to a GitHub connect / install screen.
  5. Confirm GitHub is already connected (org install). Optionally uninstall and reinstall the GitHub app, then repeat steps 2–4 — same result.

Expected Behavior

Clicking Enable Bugbot should enable Bugbot for the selected org/repo (or clearly show what’s blocking enablement), not redirect to GitHub connection when the org GitHub App install is already present and healthy.

Screenshots / Screen Recordings

N/A

Operating System

  • MacOS

Version Information

Cursor Web (Automations / Bugbot settings). Not using the desktop IDE for this flow.

For AI issues: which model did you use?

N/A (Bugbot enablement / account–integration issue)

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

  • Started after switching to a Team plan.
  • GitHub App: org install. Uninstalled and reinstalled with no change.
  • Affects enabling Bugbot on any orgs (cannot enable anywhere).
  • Cursor itself otherwise works; this blocks a major reason we use Cursor (automated code review via Bugbot).

Does this stop you from using Cursor?

  • No - Cursor works, but with this issue
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Update: Marking as resolved. After several MacOS app restarts, I was able to click “Enable” from the MacOS Automations tab and enable BugBot as normal

9

@amoussa1229 Thank you following up! Let us know if this comes back, and we’ll investigate.

10

I’m having this issue. I recently upgraded to Teams to enable bugbot for all of our devs and it doesn’t seem to want to activate.

I’m trying to activate from the cloud settings, not the desktop settings.