Bugbot won't run

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

Bugbot has stopped running on my repos.

Steps to Reproduce

  1. login to github
  2. go to Connected Apps
  3. uninstall Cursor
  4. go to cursor.com
  5. add a github integration
  6. give the Cursor/Github app access to all repos
  7. visit a PR
  8. type bugbot run
  9. bugbot never arrives

Expected Behavior

bugbot should run on connected repos

Operating System

Windows 10/11

Version Information

It’s bugbot

For AI issues: which model did you use?

bugbot

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, I need a bit more info to debug this:

  1. Go to the PR where BugBot didn’t respond and leave a comment: bugbot run verbose=true. Then share the request ID you get back.

  2. Are these PRs you authored, or are they from other repo contributors?

  3. In GitHub, go to Settings > Applications > Installed GitHub Apps and make sure there’s only one Cursor integration installed. After reinstalling, a stuck or duplicate installation can cause routing issues.

  4. Check the Cursor dashboard (BugBot tab) and confirm the specific repos are still enabled after reconnecting.

The request ID from step 1 will help us trace what’s happening on the backend.

I’m seeing a similar problem, and also my Cursor Dashboard spins forever and never loads.

I’m a paying BugBot customer, but haven’t been able to get any BugBot reviews for 2-3 days?

here’s an example output from a PR

After days of bugbot not working, after creating this thread, suddenly bugbot is working……..

1 Like

The problem is back [WIP] Fix documentation to use host package name and link by Copilot · Pull Request #1 · ChrisThompsonTLDR/laravel-docit · GitHub

Hey, I see the issue is back. Last time we couldn’t get diagnostics, so let’s try again:

  1. On this PR [WIP] Fix documentation to use host package name and link by Copilot · Pull Request #1 · ChrisThompsonTLDR/laravel-docit · GitHub leave a comment bugbot run verbose=true and send me the request ID it returns.

  2. Go to GitHub > Settings > Applications > Installed GitHub Apps and make sure only one Cursor app is installed. After reinstalling, a duplicate sometimes gets left behind.

  3. Check https://cursor.com/dashboard?tab=bugbot that this repo is enabled under the BugBot tab.

  4. Try disconnecting and reconnecting the GitHub integration at https://cursor.com/dashboard/integrations. Sometimes the account link gets out of sync.

The request ID from step 1 is the main thing we need to diagnose this on the backend. Let me know how it goes.

I can’t get you a request ID. Bugbot never shows up in the PR and says anything.

This is a completely different repo. You can see at the top, Bugbot was in there. Now bugbot won’t reply.

1 Like

Hey @christhompsontldr – the complete silence (no response even on manual triggers) points to a connection-layer issue between your GitHub App installation and Cursor, not a settings problem. We also recently experienced a brief BugBot service disruption that may have contributed to the intermittent pattern.

To do a full clean reset:

  1. GitHub Settings > Applications > Installed GitHub Apps – uninstall the Cursor app from every org and personal account (check both, you may have multiple)

  2. Confirm the BugBot dashboard shows the integration as disconnected

  3. Reinstall from the dashboard to one account/org only

  4. Try @cursor-bot review on a PR

The key difference from what you’ve tried before: make sure all existing installations are removed first. Leftover or duplicate installations can block webhook delivery entirely.

@JessMartin – “You are not a member of the team that installed Bugbot” means the GitHub App is installed under a Cursor team, but your Cursor account isn’t a member of that team. Check which account you’re signed into at cursor.com/settings. If you’re on a team, ask your admin to verify your membership. If it’s a personal setup, disconnect and reinstall from your own BugBot dashboard.

If the clean reset doesn’t resolve things, email [email protected] and reference this thread please.

I uninstalled the Cursor app from all my orgs. Then I configured it on my personal org. https://github.com/ChrisThompsonTLDR/agentic-programming/pull/7 is not working.

Thanks for trying the clean reset.

I’ve dug deeper and identified a bug from our end. Our engineering team is aware and working on a fix. I don’t have a timeline yet, but I’ll follow up here once it ships.

Can you issue me a refund from the point when the bug entered production?

Please reach out to [email protected] for any billing/refund queries please. They’re better equipped to handle these requests.

Hi I’m having issues as well. Bugbot request id: serverGenReqId_579d8a72-1034-440b-a46b-390e85d6e17b

Can you please take a look, thanks