Same for me and it prevents me to use cCloud agents
@deanrie , hi! Are there any updates about this? This is really one of the major blockers for me in Cursor that makes the whole development process way slower then it could be.
Hey, unfortunately there aren’t any new updates on this bug yet. The ticket has been logged and the team is aware, but there’s no specific ETA.
I’ll update here as soon as there’s progress.
Please raise the priority of this bug fix. Thank you.
Please fix issue with selecting branches….
Just discovered this one today,
I suppose my bug post from yesterday is somewhat related (except from the GitHub Connection Request coming up).
@deanrie I think the current situation which results in Cloud Agents not being able to be used in GitLab repos (which are used by many enterprises in regulated industries) keeps multiple companies (including mine) from migrating to Cursor. (Which I’d love to! 
)
Groups in GitLab are what Organizations are in GitHub. Proper support would be highly appreciated! 
Bumping to keep this from closing.
We would still really like to use cloud agent in our GitLab group!
My cloud agent still cannot get the branches
Same issue
Hey everyone, unfortunately nothing has changed since my last update. The GitLab group projects bug still isn’t fixed.
I can see the thread keeps growing, and I get that this is a blocker for many of you. I shared fresh feedback with the team on how many users are affected to help with prioritization. There’s no ETA yet, but your reports are helping raise visibility.
The workaround is still the same. Cloud Agents work with personal GitLab projects, not group projects. I know that won’t work for most real workflows.
I’ll update the thread as soon as I have news.
Same here, please add support for GitLab groups!
Hey! The issue with GitLab group projects not showing selectable branches in Cloud Agents has been fixed. This should be working now — let me know if you’re still running into it!
The branches are selected, but I can’t create the Cloud Agent, I see the error on cursor.com/onboard
ERROR_GITHUB_NO_USER_CREDENTIALS
(it’s gitlab repo that was selected, not github)
Thanks for the update – good to hear branches are now showing up.
The ERROR_GITHUB_NO_USER_CREDENTIALS error at creation time is a known remaining issue. The branch listing fix was one piece of the GitLab Cloud Agents puzzle, but the agent creation flow still has a code path that incorrectly tries to validate against GitHub credentials instead of GitLab. Our team is aware and working through the remaining GitLab integration gaps.
No workaround for this one at the moment, unfortunately. I’ll update the thread when there’s progress on the creation side.
@mohitjain So we can just see the repos but not do anything with it? Any timeline on when this will be resolved? This whole thing feels very misleading as a Gitlab user, we were lead to believe that it would work from the descriptions on the marketing website and dashboards.
To be straightforward: the branch listing fix that shipped recently was one piece of the puzzle, but the agent creation step still has a bug where it incorrectly looks for GitHub credentials instead of GitLab ones. There’s no workaround for this at the moment.
I don’t have a specific timeline to share, but I’ve passed along the growing number of reports from this thread to help with prioritization. I’ll update here when there’s progress.
I am struggling as well with this topic and would be happy if there will be a fix as soon as possible. Actually, having all the repos in GitLab, I cannot do anything with them.
I am on the Ultra plan. Account email: [email protected].
Important clarification: the local agent in Cursor works fine. Only the cloud / background agent fails. When I start Background Composer from a snapshot, the flow errors out immediately.
Request ID: 56f06251-cebd-4514-b2dc-f621a5a5895f
Full error payload:
{“error”:“ERROR_GITHUB_NO_USER_CREDENTIALS”,“details”:{“title”:“Failed to get service account access token”,“detail”:“Failed to get service account access token for any user.”,“additionalInfo”:{},“buttons”:[],“planChoices”:[],“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}
Additional message: Failed to get service account access token for any user.
ConnectError: [unauthenticated]
The stack trace in the app points to:
- startBackgroundComposerFromSnapshot
- _createAgentReal
Environment:
- OS: Windows
Integrations (Settings):
- GitLab: connected (e.g. as Baburin_Dmitriy)
- GitHub: not connected (shows “Connect”)
I use GitLab for my repositories. The error code mentions GITHUB.
I have tried signing out and back into Cursor. Local agent behavior is unchanged (still OK); cloud agent still fails with the same error.
Please investigate using the Request ID above and advise what I should configure, or fix on your side if this is unintended.
Thank you,
Dmitriy
Text Error:
Request ID: 56f06251-cebd-4514-b2dc-f621a5a5895f
{“error”:“ERROR_GITHUB_NO_USER_CREDENTIALS”,“details”:{“title”:“Failed to get service account access token”,“detail”:“Failed to get service account access token for any user.”,“additionalInfo”:{},“buttons”:[],“planChoices”:[],“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}
Failed to get service account access token for any user.
Error
ConnectError: [unauthenticated] Error
at t (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:66454)
at async Object.startBackgroundComposerFromSnapshot (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29268:4386)
at async bEm._createAgentReal (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%B8%D0%B9%20%D0%91%D0%B0%D0%B1%D1%83%D1%80%D0%B8%D0%BD/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45404:48209)