Hey, thanks for the report. This is a known issue. The GitHub installation token on our backend can sometimes expire or not match, so Cloud Agents can’t access org repos even after reinstalling the GitHub App.
A few 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
To help us debug this on the backend, could you share:
- The installation ID from the error (you mentioned it was redacted. We need it to find the issue on our side)
- The request ID from one of the failed attempts (from the URL on cursor.com/agents)
- Does this affect all repos in your org, or only some?
Unfortunately, there’s no reliable workaround right now. Reinstalling the GitHub App sometimes temporarily fixes specific repos, but like you noticed, it’s inconsistent.
I’ll post an update here as soon as we have more info.