Hey, this is a known issue. The GitHub installation token on our backend sometimes fails to resolve correctly, which causes the “Error loading default branch” error during Cloud Agent setup.
Several other users have reported the same thing:
- Cloud Agents cannot load default branch during environment setup and lose write access to GitHub despite correct App installation and org permissions
- Failed to determine repository default branch
The team is aware. No ETA yet, but reports like yours help with prioritization.
To help us debug on the backend, could you share:
- The Request ID from a failed Cloud Agent run (from the URL on cursor.com/agents)
- Which repo(s) are affected. Is it all repos in your org, or only specific ones?
- Have you tried reinstalling the Cursor GitHub App? (Note: this sometimes temporarily fixes things but isn’t reliable)
Unfortunately there’s no solid workaround right now. Retrying after some time sometimes works. Let me know if you can share those details.