Cloud Agents require GitHub connection and cannot access GitLab branches

[bastiamponsah (Sebastian Amponsah-Groß)]

Hi Cursor team,

I’m experiencing issues using Cloud Agents with a GitLab repository.

Where does the bug appear (feature/product)?

• Cursor IDE
• Background Agent (Web / Cloud Agents)

Describe the Bug
When trying to use Cursor Cloud Agents with a GitLab repository, the system requires a GitHub connection even though the repository is hosted on GitLab. The UI shows a message stating that Cloud Agents require access to a GitHub account, and clicking “Refresh Status” results in “GitHub access refresh failed.”

Additionally, in the Cursor Web UI I can select the GitLab repository but cannot access or select branches. The branch selector remains empty or unresponsive, which prevents running Cloud Agents against the repository.

Steps to Reproduce

1. Open a project in Cursor IDE that is cloned from a GitLab repository.

2. Start a new Agent task using Cloud Agents.

3. The UI displays: “Cloud Agents require access to your GitHub account.”

4. Click “Refresh Status” → it returns “GitHub access refresh failed.”

5. Open the Cursor Web UI and select the same GitLab repository.

6. Attempt to select a branch → the branch selector does not populate.

Expected Behavior
Cloud Agents should work with GitLab repositories without requiring a GitHub account connection. The system should allow selecting branches from the GitLab repository and starting agent tasks normally.

Screenshots / Screen Recordings
Attached screenshots show:

• Cursor IDE prompting for GitHub connection while using a GitLab repository
  “GitHub access refresh failed” error
• Cursor Web UI showing GitLab repository selected but branch selector not working

Operating System
MacOS Tahe Version 26.3 (25D125)

Version Information

Version: 2.5.26 (Universal)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

CLI:
CLI Version: not used

For AI issues: which model did you use?
GPT-5.3 Codex

For AI issues: add Request ID with privacy disabled
Request ID: e6d64464-a17c-4d5d-875b-c57ffec4201d

Additional Information

• Repository host: GitLab.com
• Repository: aquaty-capital/aquaty-frontend
• Repository works normally when cloned locally via git
• Issue occurs both in Cursor IDE and Cursor Web UI when attempting to use Cloud Agents

Does this stop you from using Cursor?

• Yes, cloud agents & environments are mandatory for us

[system]

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

• Cursor IDE
• Cursor CLI
• Background Agent (GitHub, Slack, Web, Linear)
• BugBot
• Somewhere else…

---

Describe the Bug
A clear and concise description of what the bug is.

---

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

1. …
2. …
3. …

---

Expected Behavior
What is meant to happen here that isn’t working correctly?

---

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

---

Operating System

• Windows 10/11
• MacOS
• Linux

---

Version Information

• For Cursor IDE: Menu → About Cursor → Copy
• For Cursor CLI: Run agent about in your terminal

IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

---

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

---

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

---

Additional Information
Add any other context about the problem here.

---

Does this stop you from using Cursor?

• Yes - Cursor is unusable
• Sometimes - I can sometimes use Cursor
• No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

[bastiamponsah (Sebastian Amponsah-Groß)]

thanks! edited

[bastiamponsah (Sebastian Amponsah-Groß)]

Update: tried another prompt; now it showed at least the GitLab Connection requirement where before only GitHub was. But still failing.

Precondition, I removed the GitHub integration, which was connected before.

[James_Eyre]

I also have the same problem.

Hoping for a quick fix!

[bastiamponsah (Sebastian Amponsah-Groß)]

update as of today March 20th, still not working (branches not showing up),

Seems to be backend related rather than Cursor client (tested in Web as well), Desktop client is Cursor Version: 2.6.20 (Universal).

[Robby_Ferguson]

Experiencing the same issue with our self-hosted Gitlab instance. Connecting to the instance seems to work fine (some UI bugs, but repos show correctly). When I go to try to initiate a cloud agent session, I get the same message as the OP about GitHub credentials not being found (we don’t use GitHub, and it’s never been connected to our Cursor infrastructure).

[Juan_Fernando_Schuss (Juan Fernando Schussmüller)]

hi! got the same problem, any news?

[bastiamponsah (Sebastian Amponsah-Groß)]

hey fellow commenters, AFAIK this one is connected: Gitlab cloud agent - #32 by deanrie.

so Cursor Team is aware of the bug via @deanrie and is keeping the sibling-thread updated.
But currently unfortunately no ETA for fix

[deanrie]

Hey, thanks for the detailed bug report and screenshots. I can see both the GitHub access refresh failed error and the empty branch selector in the Web UI.

This is a known issue. Cloud Agents are currently trying to validate GitLab repos using GitHub credentials, and branches for GitLab group scoped projects aren’t showing up. The team is aware and the bug is logged, but there’s no specific ETA yet.

Like you found, the main thread on this is Gitlab cloud agent Gitlab cloud agent

Let me know if you have any questions.