Cursor

Setting up a Cursor integration lets you can ask Cursor about your product's code directly in Plain. The Cursor integration lets you and Sidekick ask questions about your codebase(s) to help troubleshoot and resolve customer issues faster.

What it does

The Cursor integration connects Plain with your GitHub repositories through Cursor's AI-powered code analysis. You can ask questions like "How does the password reset flow work" or "What API endpoints handle user authentication?" and get answers based on your actual code.

This is especially useful when:

• A customer reports a bug and you need to understand what the code does

• You need to verify how a specific feature is implemented

• You want to suggest troubleshooting steps based on the actual code paths

• You're looking for specific implementation details to help answer technical questions

Setting up your API key

You need to be a workspace admin to set up the Cursor integration.

Step 1: Enable Plain AI

The Cursor integration requires Plain AI. If you haven't already:

1. Go to Plain AI settings

2. Click Enable Plain AI

Step 2: Get a Cursor API key

1. Log into Cursor

2. Go to Dashboard → Integrations

3. Ensure you have connected GitHub to Cursor. The repositories you allow Cursor to access in this step will determine what codebases it can look up via Plain.

4. Generate a new User API Key.

5. Copy the key (it starts with key_)

Step 3: Add your Cursor API key to Plain

1. In Plain, go to Settings → Integrations → Cursor

2. Paste your Cursor User API key

3. Click Connect Cursor

Anyone in your workspace can now ask questions from Cursor on any thread.

How it works

Asking questions yourself

You can launch a Cursor agent from a thread page as follows:

1. Click Ask Cursor button in the thread sidebar under Actions (or press Cmd + K and search "Ask Cursor")

2. Type your question – note that Cursor won't automatically get the context of the thread you're on, so include any relevant details from the customer as needed.

3. Select which repository you want to search

   When you ask a question, you select which GitHub repository to search. Make sure you pick the repo that contains the relevant code for your question.

   If your product uses multiple repositories (like separate frontend and backend repos), you might need to ask separate questions for each one.

4. Click Ask

The Cursor agent runs in the background and searches your codebase. When it's done, you'll see the results in the thread timeline. The thread automatically moves to "Close the loop" status so you can come back to review the answer.

Asking questions with Sidekick

You can also let Sidekick ask Cursor for any relevant information – just ask. Sidekick can also proactively suggest asking Cursor when it thinks codebase knowledge would help. It might say something like "Should I check with Cursor about how the payment flow works?"

Sidekick will let you know the question has been sent, and the thread will move to "Close the loop" when the Cursor agent responds.

What to ask

Good questions for Cursor are specific and focused on understanding how the code works:

• How does the user authentication flow work?

• What happens when a payment fails in the checkout process?

• How do we validate email addresses in the signup form?

• What error handling do we have for API timeouts?

Less effective questions:

• Very broad questions like "How does the app work?

• Questions about user data (Cursor only reads code, not databases)

• Questions better suited for your documentation or past threads

The more specific your question, the more useful the answer will be.

Reviewing agent responses

Questions asked from Cursor will appear in the thread sidebar under Actions. Sidekick will also proactively make use of any existing Cursor agent responses when summarising threads or making suggestions.

At the moment, Ask Cursor is limited to a single response per question – you cannot ask follow-ups. When Cursor isn't able to answer your question well, ask a new one, providing more information as needed.