Where does the bug appear (feature/product)?
BugBot
Describe the Bug
Product: Cursor Dashboard → Settings → Bugbot
Repository provider: Bitbucket Cloud
When enabling Bugbot for a single repository via the per-repo toggle, the action fails with a credentials scope error. However, using the bulk actions Enable All and Disable All on the same page works correctly.
This suggests the individual toggle and bulk actions may be using different API paths or permission checks.
Steps to Reproduce
- Open Cursor Dashboard → Settings → Bugbot
- Select the repository whose Source Control Provider is Bitbucket Cloud
- Locate the repository
- Toggle the individual switch for that repository ON
- Result: Error toast appears (see the left hand side of attached screenshot).
Use Enable All on the same page
Result: All repositories, including automindhispos/hispos, are enabled successfully. (see the right hand side of attached screenshot).
Use Disable All
Result: All repositories are disabled successfully.
Try toggling a single repository again
Result: Same error as in step 4.
Expected Behavior
The per-repo toggle should enable/disable Bugbot for a single repository, consistent with Enable All / Disable All.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
N/A, issue on Cursor Dashboard https://cursor.com/dashboard/bugbot
Additional Information
I am an administrator of the Bitbucket repository.
The error references missing repository:admin scope, but bulk enable/disable succeeds on the same page with the same account/session.
This inconsistency makes it look like a product bug rather than a pure permissions issue on our side.
Possible causes:
Individual toggle uses a different Bitbucket API endpoint that requires repository:admin
Bulk actions use a different code path that does not require repository:admin
Stale or inconsistent credential scopes between single-repo and bulk operations
Does this stop you from using Cursor
No - Cursor works, but with this issue