Where does the bug appear (feature/product)?
BugBot
Describe the Bug
I recently configured bug bot to run on all my organizations repos - however, I’m getting the comment: “Skipping Bugbot: BugBot is disabled for this repository” when calling bugbot on a PR that was opened BEFORE I enabled this setting. Is there a way to force a refresh for permissions? Does this take some time to propogate?
Steps to Reproduce
- Create a repository
- Create a PR
- Enable bugbot
- Run bugbot
Expected Behavior
bug bot should run.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.5
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z (6 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Additional Information
No
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hey! This sounds like it may be a bug. Can you confirm that in your Bugbot dashboard, Bugbot is enabled for that repo? And then do a “bugbot run verbose=true” and send me the request ID if it fails please!
The comment was:
Bugbot request id: serverGenReqId_4c7f02de-7196-46b8-b364-915da020e24b
I’m seeing that you have Bugbot enabled for exactly 1 repo, are you sure your PR is in that repo? You can check in your dashboard at Cursor - The AI Code Editor
I can’t see much more since your org has privacy mode enabled, but happy to hop on a call and help troubleshoot if you’re sure this is the same the repo that has Bugbot enabled.
Thanks this helped! I think the UX was a little confusing, because when I was enabling repositories 1-1 it would automatically flip on, but when I enabled all repos it forced me to toggle.
It forced you to toggle what? Sounds like we may have had a bug here! Glad you were able to get it working, keep me posted if you’ve got more feedback!!
I’m seeing this same issue @jkaplan - my repo is enabled in the Cursor dashboard for BugBot. I’m seeing “Skipping Bugbot: Unable to authenticate your request. Please make sure Bugbot is properly installed and configured for this repository.” In the “Checks” tab on GitHub I see this:
Bugbot Analysis Progress (41s elapsed)
Gathered PR context (3s)
Analyzed code changes (1s)
Bugbot run failed (37s)
Result: Bugbot failed to run
Request ID: serverGenReqId_f0747848-9900-470f-aa16-405700705619
Hey! The error I see is a provider overload error, likely transient. Does Bugbot work for you now? We should improve our error messages in this case, good feedback for us.
Thanks for getting back to me. I did another PR and BugBot worked for that one - however, in the original PR that I noticed this issue in, I just tested it again and I’m seeing the same issue:
Bugbot request id: serverGenReqId_e6ff3578-6fae-4dbb-aec7-ae4cc701b8a1
Skipping Bugbot: Unable to authenticate your request. Please make sure Bugbot is properly installed and configured for this repository.
If this is some transient error then I’ll try it again later. Edit: I’ve tried again now, 5 hours after making this reply, and it’s still happening. It’s almost as if this one specific PR just will not work, while other PR’s work fine. Strange. Most recent request ID: serverGenReqId_4d75b639-013f-4e45-82cb-13b38d915e60
Are these PRs in the same repo? Or is the failing one in a different repo which does not have Bugbot enabled? Can you check your Cursor dashboard just to make extra sure that Bugbot is on for that repo?
This is all in one repo, and only one particular PR has this issue (no other PRs in the same repo fail like this). The repo is indeed enabled.
In the branch “1.3” I’ve just made a new PR, and it seems to be working:
Although, on branch “1.3-point-photos-fix” I cannot get this PR to work with BugBot (I’ve since merged/closed the PR, but it failed many times prior to closing as well - this is what caused me to come post here originally):
So, I’ve just created a new PR on that same branch, “1.3-point-photos-fix”, to see if it’s the branch that is broken, or just that specific PR, and this new PR works perfect:
As far as I can tell, this issue is isolated to a specific PR. Not a big deal for my specific case here, but I think I’m doing everything right.. so just an odd bug?
Very interesting. Thanks for sharing and I’m glad this isn’t a big blocker for you. Will note this though 
Hey @jkaplan I’ve figured out (I think) what the issue was here. When I request bugbot run using my GitHub account “natenubble” (a contributor to the repo) it works, but not when I request bugbot run under the repo owner account “nubblesite”. I guess some permission issue? The account that works uses the same e-mail as I use on Cursor.
1 Like
