Hey Jake, thanks for the details, that helps narrow down the possible causes.
Two things stand out right away:
- The “no webhooks” line is the key clue. On GHE, Bugbot gets PR events via webhooks that are set up automatically when you install the Cursor GitHub App. If your GHE isn’t sending webhook deliveries for the Cursor App, Bugbot simply can’t know a PR was opened, and that matches what you’re seeing.
A couple common things to check, in order:
- Make sure the Cursor App is installed at the organization level, not the enterprise level. GitHub Apps installed at the enterprise account level don’t receive repo activity webhook events at all. They only cover enterprise level events. So even if everything else looks right, installing via the enterprise admin UI means PRs will never trigger Bugbot. The app needs to be installed on the OpenLaw organization where the repos live. Link: Installing a GitHub App on your enterprise - GitHub Enterprise Cloud Docs
- Then check App > Advanced > Recent Deliveries on your GHE: Site Admin > All apps > Cursor app / cursor-bugbot. Open a new PR and see if a delivery shows up and what response code it gets. No deliveries means an install or scope issue. 4xx or 5xx means a routing issue on our side.
- Your screenshot shows two GHE entries, which is unusual:
- OpenLaw (GitHub Enterprise) with 50/50 repositories enabled
- cursor-bugbot (git.openlawhq.com) (GitHub Enterprise) with 0 repositories available
Only one of these should map to git.openlawhq.com. The fact that cursor-bugbot (git.openlawhq.com) shows 0 available repos looks like the app installation can’t see any repos, most likely due to permissions or the wrong install scope. Meanwhile, the OpenLaw entry with 50/50 enabled is probably an old or duplicate connection from a previous reconnect attempt, so toggling repos there doesn’t actually bind anything to your self hosted instance. We’ve seen similar routing issues caused by duplicate installs, for example:
- Bugbot not working after reinstall - disabled in all repositories
- GitHub Enterprise integration broken after Cursor app reinstall
Can you check the following:
- Open the OpenLaw entry. What host does it actually point to, and do the listed repos look like the real repos on git.openlawhq.com or something else?
- On the GHE side, confirm the Cursor GitHub App is installed on the OpenLaw organization, not at the enterprise level, with access to the repos that have PRs
- Check Recent Deliveries on the app right after opening a fresh PR
Once we know which entry is the live one, and whether the app is installed in the right scope, we can clean up the duplicate on our side if needed.