I’m not sure if this is a bug or a misunderstanding of the bugbot integration settings. I have my bugbot settings like this:
But PRs are getting commented on even if no one says BugBot run - and it is giving feedback even when no issues are found - I assumed those were organization wide settings, is that not accurate?
Hey! These are personal settings (note the language in the header that says this is specific to how BugBot works for you). Are you seeing these settings not being respected for you, or just for other people in your org?
For other people. Is there a way to set default or global versions of these settings?
Currently no, but definitely open to feedback here. Curious to hear more about why you’d like to do that. These settings feel very personal to how you’d like BugBot to behave for you, whereas others in your org might like the “no bugs found” comments and want it to run automatically.
I just raised a similar thread, apologies that I missed this one before I posted!
I am the admin for my team and I absolutely assumed that these were organisation-wide settings. We work as a team and all want the same behaviour. I would never assume that every member of my team needs to go in here and set this up.
For my team it’s a cost issue, we don’t want it running on every push for anyone.
Yes, exactly this - I am the admin, and assumed I had more control, at least on defaults. I would say it’s both cost and experience:
OK, turning on allow list settings for now so folks have to turn it on manually. Feedback:
Hey all, thanks for the feedback! Will definitely consider having “only run once per PR” be an admin-level setting, and maybe turn off the trial notice on each message. We think it’s important to be transparent about pricing so wanted to make sure people have up-front notice when their trial is expiring, but maybe it’s too much noise.
To address the other point: We can’t limit BugBot to only Cursor users since we don’t have any way to know which GitHub user is a Cursor user. The only way to do this would be to require each BugBot user to go into Settings and auth with GitHub. This flow is available if you enter Allowlist mode – you can add users this way, or they can go into their settings and click “Add Me” to add themselves.
As always, thanks for the feedback and we’re excited for you to use BugBot!
For the exact reason that some GitHub users won’t have corresponding Cursor user accounts, those individuals have no way to configure their personal preference, so I think we need team level setting only configurable by Cursor team admin.
That team level setting exists in the form of the allowlist/blocklist to control who gets access. Will definitely note your feedback and see if we can do more to give admins more granular controls, but we think this setup should work for almost all cases!
Chipping in the first time in the cursor forum. Big fan, love the 1.0 update!
Not having the ability to pre-configure bugbot for everybody in the org with defaults is very painful for me, as some devs have e.g. copilot or cline, and they still have bugbot printing “no bugs found” in their PRs, cluttering things. Would love if you could reconsider giving org admins the chance to set defaults for everybody in the org, especially if they can not even configure if they have no cursor account themselves.
Thank you for all the work you put in!
Hey! Thanks for the feedback and super glad you’re loving the 1.0 update! Curious what you mean by this request though. BugBot can find bugs on your PRs regardless of if the person is a Cursor user. In fact, we have no way of knowing which GitHub user is a Cursor user unless they go into their Settings and Connect GitHub. As a result, when a team admin enables BugBot on a repo, they are enabling it for everyone contributing to that repo, not just Cursor users on their team.
This is why we give you the option to turn on an Allowlist. If you’d like to restrict it to certain users, just turn that on and either add the GitHub usernames manually yourself, or have your teammates connect with GitHub on that tab and click the “Add Me” button that they’ll see next to the Allowlist.
As always thanks for the feedback and keep me posted if you have more questions!
Good morning (from central europe 
)!
Concretely, I mind the settings here:
As an admin, I’d want to be able to set the default to “no comments if no bugs found” - but if i understood correctly i can not do that at this point in time and it is not planned either.
Does that clarify things?
Yes unfortunately that’s not planned right now. We think it’s very useful to know if BugBot found no bugs and it’s a nice signal! If an individual user wants to turn it off they can, but we don’t currently see reason for that to be admin-controlled.
Understood, thanks for the prompt reply!
Then i’d just add my voice to the people who’d find that very very useful
FWIW, cost is the main thing here. We tried enabling bugbot for 100$ just to see what it would cost, over most (but not all) of our repos where it’d be most useful, and we ran out of budget in 5 hours with only ~40 of our engineers (EMEA) doing daily work on a tuesday morning. Without the ability to limit re-runs (or even to limit to on-demand-only), we have to disable bugbot for our entire company until these settings are available. It’s simply far too expensive in current form.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
