Dispatch a Cloud Agent

Opening an issue in a local coding tool keeps you in the driver's seat. Dispatching a cloud agent means you don't have to be. Send the issue to Cursor, and the agent reads the debug package, writes the fix, and opens a pull request — while you move on to the next problem.

📘

Before you start: Dispatching requires a Cursor API key configured at the project level by an admin, or a personal key set in your user settings. You also need an active Cursor account with API access, and the repository must be configured in Cursor.

Supported targets

• Cursor (available today)
• Claude, Codex, Devin, and others (coming soon)

How to dispatch an agent

1. Open the issue you want to dispatch.
2. Click Send to Cursor Cloud Agent in the issue header.
3. Cursor creates the agent with the LogRocket prompt and debug package link.
4. The agent's status updates inline in the LogRocket issue as it runs.

Dispatch agents on as many issues as you want in parallel — each one is tracked independently. Say you have ten open issues flagged as regressions. Dispatch an agent on each one. While you're in a planning meeting, Cursor works through them in parallel. You come back to a queue of draft PRs.

Configuration

Dispatching cloud agents requires a Cursor API key. Set it at the project level, per user, or both.

Project-wide API key (admins only)

Admins configure the project-wide Cursor API key under:

Settings → Integrations → Coding Tools → Cursor Cloud Agent

Every project member uses this key by default when they dispatch an agent.

Use a Cursor service account API key. A service account is a non-personal Cursor identity that won't break if a teammate leaves or rotates their credentials. Personal API keys work, but a service account is what we recommend for a shared team integration.

Personal API key (per-user override)

Any user can override the project-wide key with their own personal Cursor API key, set in their LogRocket user settings. Agents you dispatch run under your personal Cursor account — useful if you want runs attributed to you, or if you want to use a different Cursor seat than the team default.

To set it:

1. Open your user settings slide-out.
2. Find the Cursor API key field under Coding Tools.
3. Paste your personal Cursor API key and save.

To revert to the project-wide key, clear the field and save.

Auto-dispatching agents (private beta)

LogRocket can dispatch agents automatically based on issue criteria you define — no manual dispatch required. This is currently in private beta.

When auto-dispatch fires, it always uses the project-wide API key — never an individual user's personal key.

If you're interested, contact your LogRocket account team.

Troubleshooting

"Send to Cursor Cloud Agent" 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 doesn't have access to the repo the issue points to.
• Cursor is reporting an outage — check Cursor status.

Status isn't updating in LogRocket. Cursor pushes status updates back on a polling cadence. Give it a minute. If it's been longer, refresh the issue page; if still stuck, contact LogRocket support.

I'm an admin and I don't see the Cursor settings. Make sure you're in the right project. Project-wide integrations are scoped to a single LogRocket project at a time.