Skip to main content

Integration

Cursor session files: what they contain

Exported Markdown or a user-selected local SQLite snapshot

Supported data

Markdown metrics depend on exported detail. SQLite imports accept only known schema signatures and reject unknown Cursor versions.

Privacy

Raw prompts, responses, attachments, local paths, and source files stay on your device in either privacy mode. The only thing stats-with-titles adds is the conversation title.

Limitations

Provider export formats may change. Unknown fields are preserved as warnings instead of silently invented metrics.

Duplicate prevention

Re-imports use stable provider session identity and content normalization hashes. Container file checksums never define session identity.

Metric quality

Unavailable values remain null. Estimates are labelled estimated and exact values are never fabricated.

Troubleshooting

If detection fails, use the preview warnings and confirm the export source/version before importing again.

What a Cursor export can tell you

Prompts
Available
Counted from user headings in a Markdown transcript, or user rows in the workspace snapshot.
Responses
Available
Counted from assistant headings in a Markdown transcript, or assistant rows in the workspace snapshot.
Tool calls
Sometimes
A Markdown transcript labels tool and command turns, so they are counted and an absence is a real zero. A workspace snapshot only reports them when its rows spell each turn out as content parts; older rows that store plain message text leave the count unavailable rather than claiming zero.
Agents launched
Not in export
Background Agent chats are not present in regular local history, and neither accepted input records a subagent launch.
Tokens
Not in export
Neither the Markdown export nor the recognized workspace snapshot carries token usage.
API-equivalent cost
Not in export
Cost is priced from token counts, and this export carries none. A figure invented without them would be guesswork wearing a currency symbol.
Models
Available
Read from the model line in a Markdown transcript, or the model field on a snapshot row.
Summed session span
Available
First to last timestamp found in the transcript or snapshot.
AI active time
Not in export
Neither accepted Cursor input records per-turn durations, only instants.
Estimated interaction time
Available
Estimated from the gaps between consecutive timestamps, with each gap capped.
User active time
Not in export
No export records how long you spent reading or typing. It could only be inferred by subtracting one estimate from another, and an inferred number shown as a measurement would be a fabrication.
Waiting time
Not in export
This export stamps each message with a single instant, never a start and a stop, so no waiting or working interval can be measured.
Project grouping
Available
Sessions are grouped under a provider inbox: this export names no repository or workspace to group by.