# Gitlab cloud agent **URL:** \ **Category:** Bug Reports\ **Created:** [November 22, 2025, 5:56am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689 "2025-11-22T05:56:47Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![sadeghpro](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@sadeghpro](https://forum.cursor.com/u/sadeghpro)\ **Post date:** [November 22, 2025, 5:56am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/1 "2025-11-22T05:56:47Z")
### Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) ### Describe the Bug I’ve connected my gitlab to the cursor but when I try using the cloud agent for gitlab repository, there is no branch. I even tried the cloud agent API but I got this error Failed to validate access to repository xxx/xxx. Please check repository access and that Cursor GitHub App is installed. I was trying to use gitlab repository but as you can see it said try connect github app ### Steps to Reproduce connect to gitlab account. go to the cloud agent page. select a repository there is no branch ### Operating System Linux ### Current Cursor Version (Menu → About Cursor → Copy) Version: 2.0.77 VSCode Version: 1.99.3 Commit: ba90f2f88e4911312761abab9492c42442117cf0 Date: 2025-11-13T23:10:43.113Z Electron: 37.7.0 Chromium: 138.0.7204.251 Node.js: 22.20.0 V8: 13.8.258.32-electron.0 OS: Linux x64 6.14.0-35-generic ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [November 22, 2025, 12:01pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/2 "2025-11-22T12:01:48Z")
Hey, thanks for the report. The error message is a bit confusing, but this is actually a feature limitation rather than a bug. GitLab is currently only supported for BugBot, not for Cloud Agents or Background Agents. Cloud Agents only work with GitHub repositories right now, which is why you’re seeing a GitHub-specific error message and no branches appearing. Your options: - Use BugBot with GitLab: GitLab is supported for BugBot (you can connect it at [Cursor - The AI Code Editor](https://cursor.com/dashboard?tab=integrations)). - Use Cloud Agent with GitHub: If you need Cloud Agent features, you’ll need to use a GitHub repository. I’d also recommend creating a feature request for GitLab support in Cloud Agents, since other users are asking for this as well. Let me know if you have any questions about either option! ---
**Author:** ![sadeghpro](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@sadeghpro](https://forum.cursor.com/u/sadeghpro)\ **Post date:** [November 22, 2025, 8:23pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/3 "2025-11-22T20:23:19Z")
![image](https://us1.discourse-cdn.com/cursor1/optimized/3X/6/6/6602fac1e19f72cce84ffaa837cee70c22904a11_2_690x59.png) Thanks for your response, but as you can see, it has recently added. In my opinion, it’s an issue and I tried only to report it. ---
**Author:** ![fgilio](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/fgilio/32/16860_2.png) [@fgilio](https://forum.cursor.com/u/fgilio)\ **Post date:** [November 23, 2025, 11:57am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/4 "2025-11-23T11:57:46Z")
Oooh I also thought it was compatible with Cloud Agents. The copy is confusing, please fix that guys ---
**Author:** ![favll](https://avatars.discourse-cdn.com/v4/letter/f/f19dbf/32.png) [@favll](https://forum.cursor.com/u/favll)\ **Post date:** [November 24, 2025, 4:57am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/5 "2025-11-24T04:57:41Z")
Found this thread after running into the same issue. Some observations: The docs specifically mention GitLab support at [Cloud Agents | Cursor Docs](https://cursor.com/docs/cloud-agent) > GitHub or GitLab connection > Cloud agents clone your repo from GitHub or GitLab and work on a separate branch, pushing to your repo for easy handoff. The dashboard page for Cloud Agents specifically includes the option to connect GitLab. The dashboard page for Bugbot ALSO includes an option to connect GitLab. Connecting GitLab on the Cloud Agent tab apparently DOES NOT connect GitLab to the Bugbot. This begs the question why the option is even available in the Cloud Agent tab? Cloud Agents Tab: ![image](https://us1.discourse-cdn.com/cursor1/original/3X/4/e/4efea36d99a0fafc8a03514401cfdaa414860f9b.png) Bugbot Tab: ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/f/7fa224b3a5d362c533ef05c223b6a4d5f877c89b.png) - Once GitLab is connected via the Cloud Agent dashboard tab, GitLab repositories are selectable in the Cloud Agents interface ( [Agents | Cursor - The AI Code Editor](https://cursor.com/agents) ). However, once a GitLab repository is selected no branch can be selected. - Looking at the underlying API requests in the developer console, the call that fails is to `/api/background-composer/get-repository-branches`. It fails with a 500 Internal Server Error. The JSON response contains the error code `ERROR_GITHUB_NO_USER_CREDENTIALS` (yes, the error code references “GITHUB” not “GITLAB”). - On a minor note: The repository selection dropdown only includes the static option “Manage GitHub” at the bottom. This should probably be “Manage Integrations” or sth similar (in the future). ![image](https://us1.discourse-cdn.com/cursor1/original/3X/6/1/61a65975b3c67a3f96c4873a75ed32d0504c84c2.png) This all seems like the GitLab integration for Cloud Agents is a weird limbo state about to roll out? @deanrie could you clarify? I’d be happy to create a feature request, however, this is quite confusing and if possible would like some clarification first. Thank you! ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [November 27, 2025, 10:04am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/6 "2025-11-27T10:04:47Z")
Hey everyone, this should be working now. Let me know if the problem persists. ---
**Author:** ![celestialorb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/celestialorb/32/38365_2.png) [@celestialorb](https://forum.cursor.com/u/celestialorb)\ **Post date:** [November 27, 2025, 7:07pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/7 "2025-11-27T19:07:40Z")
I’m still seeing the same behavior. I can select a GitLab repository in a new agent, but I cannot select a branch. The dropdown component for selecting a branch is still disabled. ---
**Author:** ![favll](https://avatars.discourse-cdn.com/v4/letter/f/f19dbf/32.png) [@favll](https://forum.cursor.com/u/favll)\ **Post date:** [November 28, 2025, 3:13pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/8 "2025-11-28T15:13:13Z")
Hello @deanrie, thank you for your quick reply. I ran into the same issue and conducted some further testing. Before testing again, I disconnected the GitLab integration from the Cursor Dashboard and I also revoked the Cursor application from within GitLab (Preferences \> Applications \> Revoke). - Newly created personal projects under my own user namespace **work** , and I can select branches from the dropdown menu in the agents interface. - However, for the following types of projects the agents interface still won’t allow me to select a branch. The same `ERROR_GITHUB_NO_USER_CREDENTIALS` error is observable in the developer console. Note: I am using the terms “old” and “new” to describe groups and projects created before and after your recent update respectively: - Old group projects created in old groups - New group projects created in old groups - New group projects created in new groups - I couldn’t test personal projects created before your update since I didn’t actually have any in my GitLab account. So, there still appears to be an issue with projects created in groups. Personal projects seem to work fine. Thank you for your quick work on this. ---
**Author:** ![loris\_shaarp](https://avatars.discourse-cdn.com/v4/letter/l/bcef8e/32.png) [@loris\_shaarp](https://forum.cursor.com/u/loris_shaarp)\ **Post date:** [December 12, 2025, 7:03am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/9 "2025-12-12T07:03:40Z")
I confirm the bug occurs with GitLab group projects. On my side, it’s the same. ---
**Author:** ![NorthCat](https://avatars.discourse-cdn.com/v4/letter/n/a9adbd/32.png) [@NorthCat](https://forum.cursor.com/u/NorthCat)\ **Post date:** [December 13, 2025, 5:24am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/10 "2025-12-13T05:24:15Z")
I can confirm the issue, I’m having it as well, not be able to choose a branch in a project created under a project group. ---
**Author:** ![celestialorb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/celestialorb/32/38365_2.png) [@celestialorb](https://forum.cursor.com/u/celestialorb)\ **Post date:** [December 16, 2025, 8:42pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/11 "2025-12-16T20:42:08Z")
Confirmed the same behavior on my end. Projects under my own account’s namespace work and I’m able to select a branch, but I’m not able to select a branch for projects under a group I’ve created. ---
**Author:** ![Zenko](https://avatars.discourse-cdn.com/v4/letter/z/ecb155/32.png) [@Zenko](https://forum.cursor.com/u/Zenko)\ **Post date:** [January 7, 2026, 5:23pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/12 "2026-01-07T17:23:40Z")
Can confirm same issue. ---
**Author:** ![husseinraoouf-suhyl](https://avatars.discourse-cdn.com/v4/letter/h/dc4da7/32.png) [@husseinraoouf-suhyl](https://forum.cursor.com/u/husseinraoouf-suhyl)\ **Post date:** [January 8, 2026, 3:00pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/13 "2026-01-08T15:00:18Z")
@deanrie this is blocking us from using cloud agents and slack integration with gitlab, and i think it would affect alot of users too since most people using gitlab for work will have their repos under a group, i appreciate all the work done by the cursor team and really want to use it but i am currently blocked until this issue is solved ---
**Author:** ![Pavel\_Shevtsov](https://avatars.discourse-cdn.com/v4/letter/p/c6cbf5/32.png) [@Pavel\_Shevtsov](https://forum.cursor.com/u/Pavel_Shevtsov)\ **Post date:** [January 22, 2026, 9:26pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/14 "2026-01-22T21:26:09Z")
Same here. Still fails for team GitLab repos. ---
**Author:** ![Hans\_Brouwer](https://avatars.discourse-cdn.com/v4/letter/h/ba9def/32.png) [@Hans\_Brouwer](https://forum.cursor.com/u/Hans_Brouwer)\ **Post date:** [February 2, 2026, 10:43am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/15 "2026-02-02T10:43:10Z")
Hi @deanrie, the problem does indeed persist. This is a blocking issue for us as well. Cursor Agents cannot be used via the web UI or background agents with our GitLab repository in our organization’s group. Would definitely appreciate any updates whether this will ever be fixed… ---
**Author:** ![Oliver\_Evans](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/oliver_evans/32/97551_2.png) [@Oliver\_Evans](https://forum.cursor.com/u/Oliver_Evans)\ **Post date:** [February 8, 2026, 3:28pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/16 "2026-02-08T15:28:38Z")
I’m experiencing the same issue ---
**Author:** ![nivanov](https://avatars.discourse-cdn.com/v4/letter/n/97f17d/32.png) [@nivanov](https://forum.cursor.com/u/nivanov)\ **Post date:** [February 19, 2026, 5:30am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/17 "2026-02-19T05:30:09Z")
@deanrie, hi! Any updates on this? I and many other people continue to have troubles connecting gitlab to cloud agents. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [February 19, 2026, 7:47am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/18 "2026-02-19T07:47:30Z")
Hey, sorry for the late reply and for marking the thread as solved. The issue with group projects still isn’t fixed. We’ve logged a bug: Cloud Agents can’t fetch the branch list for GitLab projects that live in group namespaces. Personal projects work, group projects don’t. It’s on our radar, but we don’t have an ETA yet. I’ve shared with the team that this is a blocking issue for several users, which should help with prioritization. I’ll update the thread when I have news. ---
**Author:** ![Jake\_Goodman](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@Jake\_Goodman](https://forum.cursor.com/u/Jake_Goodman)\ **Post date:** [February 23, 2026, 1:10pm UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/19 "2026-02-23T13:10:37Z")
Hi, just adding here that I am experiencing the same issue. My goal is to configure my Cloud Agents to default to a particular Repository in my company’s gitlab (not self-hosted, I’m talking [gitlab.com](http://gitlab.com)), and this desired Repository lives within a Group. Despite successfully connecting GitLab in the Integrations page, when I go to Cloud Agents → My Settings → Select repository, I see “No items - Manage GitHub”. So it appears like the GitLab integration is not working still for me. I am looking forward to configuring this properly when the issue is fixed! ---
**Author:** ![mike1026915](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@mike1026915](https://forum.cursor.com/u/mike1026915)\ **Post date:** [February 24, 2026, 7:38am UTC](https://forum.cursor.com/t/gitlab-cloud-agent/143689/20 "2026-02-24T07:38:00Z")
I met the same issue here. I can get the repo list from gitlab but I cannot get the branch list [Next page](https://forum.cursor.com/t/gitlab-cloud-agent/143689.md?page=2)