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.
4 Likes
Please raise the priority of this bug fix. Thank you.
1 Like
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! 
1 Like
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.
3 Likes