Skip to main content
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.
Cursor: lookup
The Cursor integration requires their Cloud Agents feature, which is only available on Cursor Pro plans (and above) at this time.

​
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.
1

Enable Plain AI

The Cursor integration requires Plain AI. If it is not on already, go to Plain AI settings and click Enable Plain AI.
2

Get a Cursor API key

Log into Cursor and go to Dashboard → Integrations.Connect GitHub to Cursor first. Whichever repositories you allow here are the only ones Cursor can look up from Plain.Generate a new User API key and copy it. It starts with key_.
3

Add the key to Plain

In Plain, go to Plain AI → Configuration → Ask Cursor, paste the key, and click Create Integration.
Anyone in your workspace can now ask questions from Cursor on any thread. Note that while the Cursor API key is scoped to a single person’s Cursor account, on Plain’s side, it’s shared by the entire workspace.

​
How it works

​
Asking questions from a thread

  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.

​
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:
  • 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. New messages from Cursor also appear in the thread timeline, so you can see responses at a glance without opening the Ask Cursor sidebar popover. Sidekick will also proactively make use of any existing Cursor agent responses when summarizing threads or making suggestions. Note that all Cursor questions and responses are visible to the rest of your team. 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.