Skip to main content

Command Palette

Search for a command to run...

Integrations

GitLab

The GitLab integration connects your repositories so you can use features like Cloud Agents and Bugbot.

Setup

Requires Cursor admin access and GitLab maintainer access.

  1. Go to Integrations in the dashboard
  2. Click Connect next to GitLab (or Manage Connections if already connected)
  3. Follow the GitLab installation flow
  4. Back on the Integrations tab, click Manage next to your GitLab connection and select Sync Repos
  5. Return to the dashboard to configure features on your repositories

To disconnect your GitLab account, return to the integrations dashboard and click Disconnect Account.

Advanced networking

Self-hosted instances support multiple connection methods beyond IP whitelisting. For setup details and supported private networking options, see Private Connectivity.

Available for Enterprise customers. Use AWS PrivateLink when your GitLab instance is in AWS or can sit behind an AWS Network Load Balancer. PrivateLink can cover Cursor accessing GitLab and, when needed, GitLab sending webhooks back to Cursor without public internet egress.

Best for: AWS-hosted GitLab instances and teams that want private VPC endpoint connectivity

Security: HTTPS encryption, AWS PrivateLink, VPC endpoint policies, service account access tokens

Drawbacks: Requires coordination with Cursor and AWS endpoint service setup.

Available for Enterprise customers. Use Cloudflare Tunnel when AWS PrivateLink is not practical or when you need an outbound-only deployment model. Cursor creates and owns the tunnel, and provides the hostname and token. You run cloudflared outbound from your network. You do not need a Cloudflare account or contract.

Best for: Environments without inbound network access

Security: HTTPS encryption, Cloudflare Tunnel, service account access tokens

Drawbacks: Requires running and maintaining cloudflared in your environment.

Commit author

Cloud Agents commit as the bot user of the project access token Cursor creates for each project, so their commits pass push rules that require the commit author to be a GitLab user. Creating that token needs Maintainer access to the project. If the token is unavailable or Cursor can't resolve its bot identity, agents fall back to Cursor Agent <cursoragent@cursor.com>, and those push rules reject the commits.

Protected Git Scopes

Lock your GitLab group or namespace to your Cursor organization so only your teams can use its repositories with Cloud Agents, automations, and Bugbot. Protecting a scope requires the GitLab Owner role. See Protected Git Scopes.

Next steps

Once your GitLab integration is connected, configure the features that use it:

  • Bugbot — automated PR reviews that catch bugs and security issues
  • Cloud Agents — AI agents that run in the cloud on your repositories