Bugbot Not Working Despite GitHub App Reinstallation

Where does the bug appear (feature/product)?

BugBot

Describe the Bug
I’m running into an issue with Bugbot. The bugbot run command has stopped responding entirely in GitHub PRs. This is happening mostly on PRs authored by others, but occasionally on my own PRs as well.

Symptoms:

  • No error messages are returned.

  • No emoji reactions or feedback appear on the comment.

  • The command fails silently.

Steps to Reproduce

  1. Open a PR (two PRs, one with another git user and one with your own)
  2. The one PR authored by yourself should automatically trigger bugbot.
  3. The PR authored by another user, send the command bugbot run or cursor review.
  4. Bugbot would not have run now.

Expected Behavior

Bugbot runs and shows up as a process running in the Checks tab of the GitHub PR. Bugbot had been working on PRs opened by other collaborators until now (I have been on the paid plan of bugbot for 2 months now). But suddenly it has stopped since yesterday.

Operating System

Windows 11 (Edge Web Browser)

Troubleshooting already attempted:

  • Uninstalled and reinstalled the GitHub app in the organization (no change). And ensured the repositories are enabled for Bugbot in Cursor Dashboard.

Logs/Debug Info:

  • Ran the command cursor review verbose=true to debug.
  • I received the following Request ID: Bugbot request id: serverGenReqId_b2d046e0-5a4a-4231-ac16-40ebcf93d2a0

Does this stop you from using Cursor?

No cursor works, but it does stop us from using bugbot which had become an important part of our SDLC.

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey, thanks for the report. I’ll need a bit more info:

  1. Which plan are you on, Individual or Teams?
  2. For the PRs that Bugbot is ignoring, are you the author, or are they from other repo members?
  3. Are the repos enabled for Bugbot in the dashboard: https://cursor.com/dashboard?tab=bugbot?

Important note about plans:

  • Individual plan: Bugbot only works on your own PRs
  • Teams plan: Bugbot works for all members in connected repos

If you’re on Individual and you’re trying to review someone else’s PR via cursor review, that’s expected. You’ll need a Teams plan. If these are your own PRs, or you’re on Teams, then it’s a bug, and I’ll escalate it to the team with your Request ID.

I am on the individual plan, and I now see that the way the plan works has changed now with the PR author requiring to be my own git user. Earlier this wasn’t the behaviour, so I was confused as to why it’s not working to review other’s PRs within the repo.

Thanks though!

Yes, I’ve seen the same while on BugBot pro, which seems to be a shortcoming of the plan I have in place.

How can I get a reimbursement? Like you can’t simply go ahead and change terms of conditions or functionality in the app AFTER I have paid and been a user for months. I understand if changes occur AFTER my subscription expires and I have to renew. But during my subscription period – this is just malpractice.

I don’t want work with a company that just simply nerfs the app randomly when terms have been agreed. It’s really rude and bad business practice.