Cursor
Open issues in Cursor locally, or configure Cursor Cloud Agents to open pull requests from LogRocket
What the Cursor integration does
The Cursor integration connects LogRocket to Cursor for two things:
- Open issues (locally) in Cursor — open any issue directly in your local Cursor app, with a prepared prompt and a link to the issue's debug package already loaded. This is a personal, one-click setting — no API key required.
- Cursor Cloud Agent — send an issue to a Cursor Cloud Agent that works the issue in the cloud and opens a pull request, without you leaving LogRocket. This requires a Cursor API key, and a Cursor account with access to the repository.
Setup
Go to Settings → Integrations, and under Coding Tools, click the Cursor card.
You also need the GitHub integration connected if you want the pull request an agent opens — and its status — to appear on the Issue. Agents will still run and open pull requests without it; you just won't see them in LogRocket.
Open issues in Cursor
This section is a personal setting — it only affects your own account, and no admin setup is required.
Enable it to show Open in Cursor on issues, and to launch your local Cursor app with a prepared prompt when you select it. See Open in an Agent Coding Tool for how this works day-to-day.
If Cursor isn't installed locally, LogRocket falls back to Cursor's web version automatically — you stay in the browser and the prompt still loads. Download Cursor here.
Cursor Cloud Agent
This section configures the ability to dispatch a Cursor Cloud Agent directly from a LogRocket issue. It can be configured at the Team level (an admin sets a default for the whole project) or overridden per-user.
Team default
| Field | What to enter |
|---|---|
| Cursor API Key | Generate a key from your Cursor account. This becomes the "Team API key" every project member uses by default when they dispatch an agent. |
Cursor Enterprise: use a service accountIf you're on a Cursor Enterprise plan, use a service account API key instead of a personal one. A service account is a non-personal Cursor identity that won't break if a teammate leaves or rotates their credentials — it's what we recommend for a shared team integration. Personal API keys work too, but aren't as resilient for team-wide use.
Repository access is managed in Cursor itself and no GitHub token is required to configure within LogRocket: the Cursor account behind the API key (team or personal) needs access to the repository, configured in your Cursor dashboard. If that account can't see the repo, the agent won't be able to work in it.
User override
Any user can override the team default with their own personal Cursor API key, set in their LogRocket user settings. Agents you dispatch then run under your personal Cursor account — useful if you want runs attributed to you, or if you want to use a different Cursor seat/API key than the team default. This override applies to manual dispatch only — auto-dispatch always uses the project-wide key. To revert to the project-wide key, clear the field and save.
Troubleshooting
"Open in Cursor" doesn't appear on issues. Check that the Cursor toggle is enabled for your account under Settings → Integrations → Coding Tools → Cursor, or under Configured Coding Tools at the bottom of the Open in… dropdown. This is a per-user setting.
Clicking "Open in Cursor" doesn't open anything. Make sure Cursor is installed and your operating system has registered its custom URL handler. The browser fallback should still work if it doesn't — if that also fails, the dropdown link still works as a regular URL you can copy.
"Create pull request with Cursor" is disabled or missing. No Cursor API key is configured for your project, and you don't have a personal one set. Ask an admin to configure the project-wide key, or set a personal key in your user settings.
The agent fails immediately after dispatch. Common causes:
- The API key is invalid or expired — rotate it in Cursor and update it in LogRocket.
- The Cursor account behind the key doesn't have access to the repo the issue points to — check this in your Cursor dashboard.
- Cursor is reporting an outage — check Cursor status.
Status isn't updating in LogRocket. Cursor pushes status updates back on a polling cadence, not instantly. Give it a minute; if it's been longer, refresh the issue page, and if it's still stuck, contact LogRocket support.
The agent finished, but I don't see its pull request. Pull request tracking on Issues requires the GitHub integration to be connected separately. The agent still opens the PR in GitHub either way — see GitHub → Troubleshooting.
I don't see the Cursor card in Settings → Integrations. Make sure you're in the right project, and that your role allows managing integrations.
Related
Looking to use LogRocket's own MCP server inside Cursor, rather than send Cursor issues from LogRocket? See the LogRocket MCP Server doc instead.
Updated 43 minutes ago