In "Slack routing" settings for cloud agents, adding a rule by team member (on teams plan) results in 400 "Failed to determine repository default branch" (and other related issues)

Support Bug Reports
, ,
1

Describe the Bug

Context
I recently upgraded individual account to a teams plan and added a new member

Bug

  • team member goes to https://cursor.com/dashboard/cloud-agents to the “Slack routing” section and selects a multi-repo environment, and hits “Add Rule”
  • this fails, 400 returned when you guys hit https://cursor.com/api/dashboard/create-slack-repo-routing-rule with the following response:
“error”: {
        “message”: “Error”,
        “details”: [
            {
                “error”: “ERROR_BAD_REQUEST”,
                “details”: {
                    “title”: “Bad Request”,
                    “detail”: “Failed to determine repository default branch”,
                    “isRetryable”: false,
                    “additionalInfo”: {},
                    “buttons”: [],
                    “planChoices”: []
                },
                “isExpected”: true
            }
        ]
    }
  • team member is unable to select a default branch … option is disabled

Tangentially Related Feedback
Y’all’s insistence on selecting / choosing a default repository does not make sense. For example, I have set up a multi-repo cloud environment (a frontend + backend repo) … selecting a “default repository” makes no sense for my use case. And yet, whenever I try to initiate a cursor cloud agent to do some work from either Slack or Linear, the agent insists on having a default repository to work from, and will refuse to proceed with the request. This makes no sense for my use case, or more generally for people working from multi-repo cloud environments.

Steps to Reproduce

discussed above

Operating System

MacOS

Version Information

https://cursor.com/dashboard/cloud-agents

For AI issues: add Request ID with privacy disabled

serverGenReqId_5040e4ee-5a40-464d-a15d-cfbb51084602

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi!

This is a known issue we’re tracking. When you add a Slack routing rule that targets a multi-repo environment, the dashboard validates every repo in that environment using the GitHub connection of the member who is signed in and clicking “Add Rule” - not the environment owner’s connection. If that member hasn’t connected their own GitHub in Cursor yet (or their GitHub account doesn’t have access to every repo in the environment), the branch check fails and surfaces as the generic 400 “Failed to determine repository default branch.”

Two ways to unblock right now:

  1. Have an admin/owner who already has GitHub connected create the routing rule. Rules are team-scoped, so it applies the same way regardless of who adds it. This is the fastest path.
  2. Have the member connect their own GitHub account in Cursor (and confirm it has access to all repos in that environment), then retry “Add Rule.” Cloud Agent actions run on behalf of the signed-in user using their own GitHub credentials, so each member needs GitHub connected. Setup steps are here: Slack integration.

On your second point: needing a single “default repository” for multi-repo environments when launching from Slack or Linear is awkward, and you’re right that it doesn’t fit a frontend + backend setup well. We’re already looking at letting routing target a multi-repo environment directly without designating one default repo.

Let me know if having an admin add the rule (or connecting the member’s GitHub) gets you unblocked.

8

Thanks Mohit. Disconnecting and reconnecting GitHub ultimately ended up working here.