Providers
Back to spooling.aiCursor
How Spool ingests Cursor sessions.
Cursor stores chat panel data inside its VS Code-style state.vscdb SQLite files.
Where sessions live
~/Library/Application Support/Cursor/User/workspaceStorage/<workspace-hash>/state.vscdb
~/Library/Application Support/Cursor/User/globalStorage/state.vscdbOn Linux: ~/.config/Cursor/User/....
What we parse
Cursor's chat data lives under workspace-scoped keys:
workbench.panel.aichat.view.aichat.chatdata: the main chat panelcomposerData:*keys: Composer/agent sessionsaiChat.chatdata: older chat-only sessions
We extract messages, sequence them by timestamp, and tag each session with the workspace folder (resolved from the sibling workspace.json if present).
Gotchas
- One session per chat panel. Cursor's internal "tabs" model means a single workspace can have several active chat sessions at once. We split each tab into its own ParsedSession.
- No tool-call detail (yet). Cursor's stored format doesn't carry the granular tool-input metadata Claude Code does, so we capture the message body but not separate tool spans. Trace view shows the flat shape.
- Workspaces stored as base64-ish hash. The directory name under
workspaceStorage/is opaque; we resolve it viaworkspace.json(which holds the original folder URI).