BitBucket repos don't appear as options in Cursor Cloud Agent routing rule

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Many of our Bitbucket repositories are no longer available to be selected when setting up a Cloud Agent routing rule. These repos stopped appearing as of today. We’re not aware of any change made to either our Bitbucket or Cursor configuration which would have caused them to disappear. We cannot determine any pattern that explains which why some of our repos are visible in Cursor while many are not.

This issue also prevents us from triggering Cursor Cloud Agents via Jira. We receive the following message in Jira when attempting to trigger for one of these missing repos:

"Cursor cannot use for this Jira request because it is not in the Cloud Agents routing context.

You are using user-level authentication. Please make sure that your Cursor account has connected the repository you’re trying to use. Alternatively, you can add a user routing rule for it in the Cloud Agents dashboard."

We’ve tried the following steps to troubleshoot:

  • Disconnect/reconnect Bitbucket integration in Cursor
  • Uninstall/reinstall Cursor Forge app in Bitbucket
  • Make Bitbucket project public

Steps to Reproduce

On the Cursor web console

  1. Go to Cloud Agents
  2. Click Add Rule
  3. Search for repo in “Select” drop down

Expected Behavior

All repositories in our Bitbucket workspace should be visible to Cursor

Operating System

MacOS

Version Information

Cursor web console

Does this stop you from using Cursor

No - Cursor works, but with this issue

9

Hey @MikeAtINFI, thanks for the detailed report and for all the troubleshooting you already did!

This isn’t caused by anything in your Bitbucket or Cursor setup, so no need to keep reinstalling or reconnecting. We’ve confirmed the behavior on our side: loading repositories from Bitbucket workspaces is currently failing intermittently, especially for larger workspaces, which is why some repos are missing from the routing-rule dropdown and why Jira runs for those repos get rejected.

The team is on it, and I’ve added your report to the existing investigation so it carries your details. I’ll follow up here as soon as there’s an update!