Can't setup Cloud Code agents with a self-hosted GitLab repository

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We’re encountering a persistent “Environment error” when attempting to run Cloud Code agents with a self-hosted GitLab repository.
The agent consistently fails during the repository cloning phase and never proceeds to execution.

Steps to Reproduce

Env:
GitLab(self-hosted) OAuth App Authorization: Authorized with scopes api and write_repository
User Access: The authorized GitLab user has access to repository
Branch Selection: The branch dropdown populates correctly — we can see and select branches from the repository
Admin Rights: Cursor admin permissions are confirmed

Actions:
go to /agents/
try to start work with any agent

Expected Behavior

The agent successfully clones the repository

Environment setup completes

Agent execution starts normally

Screenshots / Screen Recordings

blurred copy.png
blurred copy.png3838×1761 599 KB

Operating System

MacOS

Version Information

Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

GPT 5.2 Codex High

For AI issues: add Request ID with privacy disabled

request id: bc-def072f2-7224-419c-b771-21ca3683e450

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hi @Siarhei_S !

In the backend I can see a connectivity issue

fatal: unable to access 'https://redacted.com/redacted/redacted/': Failed to connect to redacted.com port 443 after 130277 ms: Couldn't connect to server

I can also see that it looks like the last time you tried was Wednesday! Are you still facing an issue?

By the way, this problem is probably better suited for [email protected]. Debugging connectivity issues to private Gitlab instances in a public forum is really not a great way to go about things.

4

Hello, @Colin

Yes, we still face this issue. We have written to [email protected]