Use ShardStitch with Cursor.
This Cursor profile covers a project instruction file and an optional local MCP connection. The key recovery check is whether the current Cursor workspace actually loaded the generated handoff.
Integration paths.
.cursorrules, auto-read by Cursor.
Auto-configured at .cursor/mcp.json for the project or Cursor globalStorage.
Start from the project file; verify stored chat context separately from repository state.
Setup path.
Generate the Cursor-targeted project instructions, open the exact repository in Cursor, and confirm the file is active in that workspace. If using MCP, check the project or user-level server configuration separately.
Generate .cursorrules, install MCP, then start a fresh Cursor chat against the recovered state.
Ask the new Cursor chat to identify the changed files and pending test from the handoff, then compare its answer with the Git panel or terminal.
Limits to know.
An instruction file does not restore Cursor chat history, and file conventions can vary by Cursor version and workspace setup. Verify what the current client reads instead of relying on the filename alone.
Best use case.
Restarting a stale Cursor chat without re-explaining every changed file.
FAQ.
Does .cursorrules prove Cursor loaded this recovery packet?
No. Confirm that the current Cursor workspace recognizes the file and that its contents appear in the session context. The project file and MCP connection are separate checks.
Resume this workflow.
After an inline-edit session becomes stale, open the same project, verify the handoff is in context, and inspect the diff before asking Cursor to continue. If only one file changed, keep the next request limited to that file and its focused test.
Check that Cursor applies the intended project instructions and that the fresh conversation has the current diff, rather than relying on a stale rule file alone.
Primary source and delivery boundary.
Cursor rules (checked September 27, 2026). Cursor documents project rules and their application. Keep durable conventions separate from a temporary checkpoint and verify the current workspace before resuming.
Tool-specific troubleshooting
For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Cursor.
More Cursor recovery guides.
Check a Cursor AI limit, a stale chat context, or a terminal command that has not finished before resuming the task.