Cursor

What it does

• Starts a Cursor cloud agent on a ticket, with the ticket’s details as its instructions.
• The agent works in the repository mapped to the ticket’s product and opens a pull request.
• The pull request link is added to the ticket for your team to review.

Before you start

• A Cursor API key from your Cursor account. Agent usage is billed to that Cursor account.
• Cursor’s GitHub access. Cursor works in your code through its own GitHub connection, set up in your Cursor dashboard — not through Worklynq’s.
• You need to be your workspace’s System Admin.

Connect Cursor

1. Open the Admin console → Connectors → Developer Connections and choose Cursor.
2. Paste your Cursor API key. Worklynq checks it and loads the repositories your Cursor account can reach.
3. Map each product to its repository.
4. Save. Cursor shows as Connected with the number of repositories.

Hand a ticket to Cursor

Cursor is started by workflow automation: in a ticket type’s workflow, add the Cursor agent action to a stage. Every ticket that reaches that stage starts an agent. You choose the instructions, and whether Cursor opens the pull request automatically.

Limits and control

• Maximum run time: Worklynq cancels an agent that runs too long. Set it in Developer Connections → Cursor; leave it blank for no limit.
• Cursor doesn’t offer a per-session cost cap, so keep an eye on your Cursor plan’s usage.
• Changes come back as a pull request. Your team decides what to merge.