Error when setting up GitLab cloud agent

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I’m getting the following error when trying to connect a GitLab repository in cloud agents. I saw a different post with the same output, which was related to the GitLab role not being at least “Maintainer," which does not seem to be related as I have the “Owner” role.

Request ID: 55c7419e-ee1a-49de-ba79-4a8362591531
{“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/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45126:72715)
at async Object.startBackgroundComposerFromSnapshot (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35531:4393)
at async kmm._createAgentReal (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35846:51495)

Steps to Reproduce

I’m just trying to connect any repository trough the web dashboard as well as through the IDE. I’m getting the same error in both cases.

Operating System

MacOS

Version Information

Version: 3.5.17
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. We dug into it using the Request ID, and the issue isn’t about the role. Owner is actually enough. It’s about the GitLab plan.

Cloud Agent creates a project access token via the GitLab API, and on gitlab.com that’s only available on Premium or higher. On the Free plan, the API returns 400 - User does not have permission to create project access token no matter what role you have. That error then bubbles up on our side as ERROR_GITHUB_NO_USER_CREDENTIALS, which is misleading. The GitHub wording and the suggestion to re-login don’t match the real cause.

Options:

  • Move the project to a group or namespace on a Premium GitLab plan
  • Use a self-hosted GitLab instance, where project access tokens are available without these restrictions

We’ve logged the misleading error on our side so GitLab shows the actual message from the GitLab API. No ETA for the fix yet, but I’ll post an update here when I have one.