Can GitLab and Cursor talk in both directions?

Yes. Build one flow that starts in GitLab and acts in Cursor, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect GitLab to Cursor

Move data between GitLab and Cursor the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore GitLab Explore Cursor

GitLab triggers: 1
GitLab actions: 2
Cursor triggers: 5
Cursor actions: 4

Automation ideas

What you can build with GitLab and Cursor

A few flows teams run between GitLab and Cursor. Use one as a starting point, or build your own from scratch.

New Project Issue Event in GitLab creates Launch Agent in Cursor
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New Agent in Cursor creates Create Issue in GitLab
Triggers when a new Cursor agent is created or when agent status changes
New Project Issue Event in GitLab creates Add Followup Instruction to Agent in Cursor
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New Agent in Cursor creates Custom API Call in GitLab
Triggers when a new Cursor agent is created or when agent status changes
New Project Issue Event in GitLab creates Find Agent Status in Cursor
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
Agent Status Equals in Cursor creates Create Issue in GitLab
Triggers when a Cursor agent has the specified status (e.g., "FINISHED", "FAILED")