# Bugbot routes to suspended personal GitHub app — repo enabled in dashboard but bot says disabled **URL:** \ **Category:** Bug Reports\ **Tags:** github, bugbot\ **Created:** [July 8, 2026, 5:50am UTC](https://forum.cursor.com/t/bugbot-routes-to-suspended-personal-github-app-repo-enabled-in-dashboard-but-bot-says-disabled/165098 "2026-07-08T05:50:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![trevsm](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@trevsm](https://forum.cursor.com/u/trevsm)\ **Post date:** [July 8, 2026, 5:50am UTC](https://forum.cursor.com/t/bugbot-routes-to-suspended-personal-github-app-repo-enabled-in-dashboard-but-bot-says-disabled/165098/1 "2026-07-08T05:50:44Z")
### Where does the bug appear (feature/product)? Bugbot / Security Review Agent ### Describe the Bug Bugbot returns “Skipping Bugbot: Bugbot is disabled for this repository” on FacilIQ/faciliq-platform-core even though the repo is enabled in the Bugbot dashboard (installation 145090698). No Cursor Bugbot GitHub check is ever created; our bugbot-gate workflow times out waiting for it. ### Steps to Reproduce 1. GitHub org FacilIQ has Cursor app installed (installation 145090698, all repos). 2. Bugbot dashboard shows FacilIQ/faciliq-platform-core enabled. 3. Personal GitHub account (trevsm) also had a separate Cursor app installation (94408150) marked Suspended. 4. Comment `bugbot run` on PR [https://github.com/FacilIQ/faciliq-platform-core/pull/44](https://github.com/FacilIQ/faciliq-platform-core/pull/44) 5. Cursor bot replies: “Skipping Bugbot: Bugbot is disabled for this repository.” Remediation attempted: - Uninstalled suspended personal Cursor app (94408150) - Cursor Integrations now shows only FacilIQ org (no personal trevsm) - Disable All / Enable All repos in Bugbot dashboard - Still fails after remediation ### Expected Behavior Bugbot should run on the PR, post a Cursor Bugbot GitHub check, and review the diff. Our CI gate (bugbot-gate) should pass once that check succeeds. ### Operating System MacOS ### Version Information Bugbot prod (GitHub PR comments). Cursor account: Ultra. GitHub user: trevsm. Org: FacilIQ. ### For AI issues: add Request ID with privacy disabled serverGenReqId\_ff2be65a-d008-4729-be65-8e12ec3b5c9d serverGenReqId\_00138d9e-d7f1-4fb1-b20f-f619571c0a35 serverGenReqId\_bc6d8ada-e217-4dbb-8fa0-f82b84d24866 ### Additional Information Installations: - FacilIQ org Cursor app: 145090698 (all repos, active) - Personal trevsm Cursor app: 94408150 (was Suspended, now uninstalled) Repo: FacilIQ/faciliq-platform-core (PR #44) Bugbot dashboard installation: 145090698 After uninstalling personal app, Cursor Integrations text changed from “FacilIQ, trevsm” to “FacilIQ” only — but Bugbot still returns disabled. Please fix backend routing / repo enablement for installation 145090698. ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [July 8, 2026, 12:14pm UTC](https://forum.cursor.com/t/bugbot-routes-to-suspended-personal-github-app-repo-enabled-in-dashboard-but-bot-says-disabled/165098/7 "2026-07-08T12:14:14Z")
Hey @trevsm, First, your GitHub connection is fine. `bugbot run` reaching Cursor Bot confirms the app is wired up correctly, so this isn’t a setup mistake on your end. The most common cause of this exact “enabled in the dashboard but disabled on the PR” split: [Bugbot](https://cursor.com/docs/bugbot) checks a repo’s enabled state against the specific Cursor account your commenting GitHub user is linked to, not across all your accounts. If you enabled the repo from one Cursor account but the GitHub user commenting `bugbot run` is linked to a different one, you’ll see exactly this. Worth checking first: 1. In each Cursor account you have, open Dashboard → Integrations and note which GitHub account is connected. 2. From the account your commenting GitHub user is linked to, enable the repo in the Bugbot dashboard, then re-run `bugbot run`. If it still skips after lining those up, that points to a separate known issue on our side where a repo’s enabled state can get stuck after a GitHub App reinstall/removal (consistent with your personal-app history). There’s no self-serve toggle that forces it un-stuck in that state - it needs a fix from our team, which we’re tracking. Reply here if you land there and I’ll flag it with your details. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 3, 2026, 5:18pm UTC](https://forum.cursor.com/t/bugbot-routes-to-suspended-personal-github-app-repo-enabled-in-dashboard-but-bot-says-disabled/165098/10 "2026-09-03T17:18:04Z")
Hey @trevsm, Following up on this one. We’ve made a number of improvements over the past couple of months to how Bugbot resolves GitHub installations and linked accounts, and the account alignment check above (enable the repo from the Cursor account that your commenting GitHub user is linked to) is still the first thing to confirm. If Bugbot is now running on your FacilIQ pull requests, no need to reply. If you’re still seeing “Bugbot is disabled for this repository” there on the latest setup, please open a new thread with the PR link and which Cursor account owns the GitHub installation, and we’ll take another look.