What is the Cursor integration?

The Cursor integration lets you mention @Cursor in any thread to start a Cursor Cloud Agent without leaving Glue. The agent reads the thread for context, runs in the cloud, and reports back with its progress and results — right where your team is already talking about the work.

You can use Cursor in Glue to:

• Kick off bug fixes, refactors, and small features from a thread where the work was already being discussed
• Keep the conversation, the agent's progress, and the final PR all in one place
• Share the agent's results with your team so the whole thread stays in the loop

Setting up the Cursor integration

Step 1: Add the Cursor app to your workspace

Locate Cursor in the App Directory, and click "Add app" to add Cursor to your workspace. If you don't see it in your directory, check with your Admin.

Step 2: Set a default repository in Cursor

Cursor sessions in Glue run against the default repository configured in your Cursor Cloud Agents dashboard. Set this up before you start your first session.

• Go to the Cursor Cloud Agents dashboard.
• Set the repository you want Cursor agents to work in as your default.

Cursor uses your default repository each time a session is initialized in Glue. You can't switch repositories mid-session — if you need Cursor to work in a different repo, update the default in your Cursor dashboard before starting a new session.

Step 3: Create a Cursor User API Key

In the same dashboard from the prior step, find the "User API Keys" setting and click "Add" to create a new API key. Copy the generated token, you will need it in the next step.

Step 4: Authorize Cursor

Each user will need to connect their Cursor account once. You'll be prompted the first time you mention @Cursor in a thread.

• Mention @Cursor in a thread and send the message.

• A prompt will appear asking you to connect Cursor to Glue. Click Connect Cursor.

• Glue will prompt you for an API key — paste in the generated token from the previous step. Click Authorize.

• You will see a confirmation message once Cursor is successfully connected.

Starting a Cursor session in a thread

Cursor works inside agent sessions — a back-and-forth side conversation with the agent that lives alongside your thread, similar to how Glue AI sessions work. You can iterate with Cursor and share results with your team when you're ready.

1. Open any thread where you want Cursor to help.
2. Type @Cursor in the message editor, followed by a prompt describing what you want it to do. For example: "@Cursor fix the timezone bug described above and open a PR."
3. Click Send to start the session.

Cursor will read the thread for context, spin up a cloud agent against your default repository, and begin working. The session sidebar will open automatically so you can follow along.

Give Cursor as much context as possible in your prompt. The more specific the ask — the file, the bug, the expected behavior — the better the result. Cursor will also read the thread, so earlier messages can help set the scene.

Image attachments are not currently supported in Cursor sessions.

Going back and forth with Cursor

Once a session is running, you can keep the conversation going in the session sidebar, just like you would with a teammate.

• Ask follow-up questions as the agent works
• Send clarifying instructions if it's heading in the wrong direction
• Review intermediate progress before sharing anything with the rest of the thread

Sharing Cursor's results with the thread

When Cursor finishes a piece of work — for example, opening a PR or producing a summary of what it changed — you can share the result with the thread so your team can see what happened.

• Click Share at the top of the session sidebar to publish the exchange to the thread.
• Glue summarizes the session for the thread and highlights key artifacts, like the PR link or any outputs Cursor produced.
• Clicking the summary opens the full session sidebar so anyone in the thread can read the details.

If Cursor opens a PR in a connected GitHub repo, the PR link will unfurl into a GitHub link preview in the thread so the team can follow its status.

Tips for working with Cursor in Glue

Start Cursor sessions in threads where the work is already being discussed. Cursor uses the thread for context, so replying to an existing bug report or feature discussion gives the agent a running start.

• Be specific about the outcome you want (e.g., "open a PR that adds a test for X") rather than vague goals.
• Mention the file, function, or area of the codebase if you know it.
• Set your default repository in the Cursor Cloud Agents dashboard to the repo you work in most often, since Cursor will use it for every session you start in Glue.
• For longer or riskier changes, review the PR in GitHub before merging, the same way you would for any teammate's work.

Troubleshooting

Cursor isn't responding when I mention it

• Confirm you've authorized Cursor for your user account by mentioning @Cursor in a thread — you should see a Connect prompt if you haven't.
• Make sure you have a default repository set in your Cursor Cloud Agents dashboard. Without one, Cursor won't be able to start a session.
• Agent sessions can only be started in threads. Try starting the session from a thread rather than a group chat or DM.

Cursor is working in the wrong repository

Cursor uses the default repository set in your Cursor Cloud Agents dashboard for every session. You can't switch repositories after a session has started.

• To change repos, update the default in your Cursor dashboard, then start a new session in Glue.

Cursor didn't see the image I attached

Image attachments aren't currently supported in Cursor sessions. Describe the issue in text, paste relevant error messages or logs, or link to the code you want Cursor to look at instead.

How do I give feedback on the Cursor integration?

Cursor is in beta, so your feedback helps shape where it goes next. You can contact our support team by opening the Help icon next to your profile picture and clicking Contact Support.