Hi @cHAuHaN-Arre,
When multiple users in the same GitHub org have connected their own Cursor accounts with the GitHub integration, the system can route the BugBot request through the wrong installation context. As a result, the backend doesn’t “see” that BugBot is enabled for the repo, even though the dashboard toggle shows it as on.
Here’s what to check:
-
In GitHub: go to your org’s Settings > Applications > Installed GitHub Apps. Make sure there’s only one Cursor integration installed for the org. If there are duplicates, remove them all and reinstall a single one.
-
Ask your team admin (the person who installed the GitHub App) to go to Dashboard > Integrations and verify the GitHub connection is properly set up.
-
If any colleagues have their own personal Cursor subscriptions with a separate GitHub integration connected, ask them to disconnect it in Dashboard > Integrations — having multiple installations for the same org causes routing conflicts.
-
After cleaning up, test with a new PR. Old PRs can get stuck due to outdated routing.
A similar issue was discussed in this thread with the same workaround steps.
Our team is aware of this routing issue. Let me know if the steps above don’t resolve it.