Docs about GitLab integration incorrectly state that Self-Managed requires Premium or Ultimate

Support Bug Reports
,
1

The GitLab integration documentation currently states:

GitLab integration requires a paid GitLab plan (Premium or Ultimate). Project access tokens, which are required for this integration, are not available on GitLab Free.

However, according to GitLab’s documentation, the availability of project access tokens differs between GitLab.com and GitLab Self-Managed:

GitLab deployment Project access tokens
GitLab.com Free Not available
GitLab.com Premium / Ultimate Available
GitLab Self-Managed Available with any license
GitLab Dedicated Available with any license
2

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)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something 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!

6

Hey, thanks for the report, you’re right.

The GitLab Premium or Ultimate requirement only applies to projects on GitLab.com, where project access tokens aren’t available on the Free plan. GitLab Self-Managed and Dedicated instances support project access tokens on any license, and Cursor’s integration works with them.

Right now, the wording on the page reads like the limitation applies to both GitLab.com and self-hosted. I’ve passed this to the team so they can update the docs and separate these cases.

One related thing to know: connecting a self-hosted GitLab to Cursor is available on the Team and Enterprise plans.