Hey, thanks for the detailed report.
This is a known routing issue. When multiple users in a GitHub org have their own Cursor accounts with the GitHub integration connected, the system can route the request through the wrong installation. As a result, BugBot “doesn’t see” that the repo is enabled.
You mentioned it started after the trial ended. It’s most likely that an old installation is conflicting with the new one.
Here’s what to check:
- In GitHub: Settings > Applications > Installed GitHub Apps. Make sure there’s only one Cursor integration installed for your org (asiainspection). If there are duplicates, remove them all and reinstall a single one.
- Ask your colleagues (especially anyone who might have connected Cursor earlier during the trial) to go to https://cursor.com/dashboard?tab=integrations and make sure their GitHub integration is disconnected.
- Then test with a new PR. Old PRs may be tied to the old routing.
A similar issue is discussed here: Bugbot says “Skipping Bugbot: Bugbot is disabled for this repository”
The team is aware of this routing issue. There’s no ETA yet, but your report helps us prioritize it. Let me know if the workaround doesn’t help and I’ll pass it to engineering to check the backend.