Skip to content
GitHub logoCursor logo

Connect GitHub to Cursor

Move data between GitHub 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.

GitHub triggers
14
GitHub actions
19
Cursor triggers
5
Cursor actions
4

Automation ideas

What you can build with GitHub and Cursor

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

  • New Pull Request in GitHub creates Launch Agent in Cursor

    Triggers when there is activity on a pull request.

  • New Agent in Cursor creates Create Issue in GitHub

    Triggers when a new Cursor agent is created or when agent status changes

  • New Pull Request in GitHub creates Add Followup Instruction to Agent in Cursor

    Triggers when there is activity on a pull request.

  • New Agent in Cursor creates Get issue information in GitHub

    Triggers when a new Cursor agent is created or when agent status changes

  • New Pull Request in GitHub creates Find Agent Status in Cursor

    Triggers when there is activity on a pull request.

  • New Agent in Cursor creates Create comment on a issue in GitHub

    Triggers when a new Cursor agent is created or when agent status changes

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in GitHub 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.