AI Coding Agents
Turn any LogRocket issue into a fix-ready prompt for your AI coding tool — locally or in the cloud.
Public docs draft — target URL:
docs.logrocket.com/docs/coding-agentsReplace[Screenshot: ...]placeholders before publishing.
Pasting a stack trace into Cursor by hand is a start. It's not the same as giving an agent the full picture of what happened. LogRocket's AI coding agents do the latter — they turn any issue into a fix-ready prompt, pre-loaded with the session activity, network requests, console output, and component context an engineer would normally gather by hand.
There are two ways to use them:
- Open in a coding tool — open the issue in your local AI coding tool (Cursor, Claude CLI, Codex, or Windsurf) so you can debug and fix it interactively. Learn more →
- Dispatch a cloud agent — send the issue to a Cursor cloud agent that opens a pull request without you leaving LogRocket. Learn more →
[Screenshot: Issue Details view with the "Open in…" dropdown and "Send to Cursor Cloud Agent" button visible]
Which one should I use?
| Open in a coding tool | Dispatch a cloud agent | |
|---|---|---|
| Where it runs | Your machine | Cursor's cloud |
| Supported tools | Cursor, Claude CLI, Codex, Windsurf | Cursor (more coming) |
| Setup | None required | Project-wide API key in Settings |
| Best for | Hands-on debugging, exploration, any code change you want to drive | Routine fixes you want delegated, working in parallel on multiple issues |
| Output | The issue opens in your tool with a prepared prompt | A PR (or work-in-progress branch) from the cloud agent |
What makes the prompt different
Galileo AI generates the prompt — and it's not a one-line stack trace. It includes a link to a debug package the agent can unpack and read on its own.
The debug package contains the context an engineer would normally have to gather by hand:
- The error and where it occurred — the exact exception, file, and line
- The user actions that led to the error — the relevant session activity in sequence
- Network requests and responses — what was in-flight around the time of the error
- Console output — logs and warnings leading up to the failure
- Component, route, and environment information — the state of the app at the moment it broke
Say a user hits a checkout error at 2am. Galileo packages the stack trace, the two failed API calls that preceded it, the console warnings from the payment component, and the route they were on. When you open the issue in Cursor, the agent already understands the failure path — not just what threw, but what caused it to throw.
That's the difference: a stack trace tells the agent what failed. The debug package tells it why.
Permissions and access
- Open in a coding tool is available to anyone who can view an issue. No integration setup required.
- Dispatch a cloud agent requires a Cursor API key configured by an admin under Settings → Integrations → Coding Tools → Cursor for project-wide access for your whole team. However, individual users can set their own Cursor API key via User Settings. Setting a personal API key will override the project-wide key..
Get started
Updated 11 days ago