Overview

The Cursor integration lets you investigate customer issues using your codebase from Copilot in the Inbox. Cursor checks the connected repository and returns findings you can use to draft a reply.

You can use it to:

• Check how a feature works when your documentation does not cover the question

• Investigate errors and unexpected behavior reported by customers

• Ask Cursor to implement a fix and open a pull request for review

Setting up the Cursor integration

Connect Cursor

First, connect GitHub to Cursor and give it access to the repositories your team needs.

1. Open the Cursor API dashboard and create a user API key

2. Go to Settings → Integrations in Featurebase

3. Find Cursor and click 'Configure'

4. Paste your key into Cursor user API key

5. Click 'Connect Cursor'

Featurebase loads the repositories available through your Cursor connection.

Choose repositories and teammate access

In the Cursor configuration:

1. Set ‘Default repository’ to the repository your team will use most often

2. Under Access, choose which teammates can launch Cursor requests

3. Choose which repositories those requests can target

The defaults are Everyone with a full seat and All repositories. Select specific teammates or repositories to restrict access. Teammates also need permission to use integrations.

The teammate who connected Cursor manages its settings and access. The connection uses their Cursor API key across the Workspace.

How it works

Investigate an issue from the Inbox

Open Copilot in the customer's conversation and ask it to investigate a specific question using Cursor. Include the repository name if your team uses several repositories.

Example: Use Cursor to investigate why this customer's CSV export returns an empty file. Check the export logic and explain the likely causes and troubleshooting steps.

Copilot prepares an Ask Cursor card for you to review:

1. Check the repository and the proposed prompt

2. Click 'Edit' if you want to change the question or add relevant details, such as the exact error message

3. Open Customer info to review the attributes that will be shared with Cursor. If no attributes are selected, the control reads No customer data shared

4. Remove attributes you do not need, or click 'Add attribute' to include relevant user, company, or conversation details

5. Click 'Approve & send'

The shared attributes start from the details you have pinned in the Inbox, with any changes you have saved for Cursor.

Cursor runs in the background. You can continue working while it investigates.

Review the findings and reply

When Cursor finishes, its findings appear in Copilot. Click 'View full breakdown' to read the detailed result, or use 'Open in Cursor' to inspect the run in Cursor.

For investigations related to the customer's issue, Featurebase also adds an internal note to the conversation and mentions the requesting teammate. General codebase questions stay in Copilot.

Copilot can use the findings to draft a customer reply. If you need a draft, ask Copilot to write one. Review and edit it before sending it to the customer.

Ask Cursor to make a fix

To change the code, explicitly ask Cursor to implement the change and open a pull request (PR).

Example: Use Cursor to add a clear error message when the export has no matching records, and open a pull request for review.

1. Review the proposed change on the Ask Cursor card and check that it shows Opens PR

2. Review the prompt and shared customer information, then click 'Approve & send'

3. When the run finishes, click 'View pull request' to review the proposed code changes

FAQs