This is a funny one. I recently migrated my Cursor setup from Windows to Mac by exporting my state.vscdb database and re-importing it on the Mac. The import was successful (all 29 conversations appear in the sidebar), but I’m unable to resume any existing agent conversations. Every attempt fails with:
“This conversation’s data is missing and can’t be restored. Start a new chat to continue. (208 missing blobs: dcf13b8c3310, 2e908c55f03c, 888ad6dba356, …)”
After investigating, I believe the root cause is that the conversation blobs are stored server-side under my Windows workspace ID, but my Mac client is querying under a different workspace ID — because the two platforms produce different hashes for my home directory folder path.
Details:
Value
Error Request ID
a7fbfab8-9565-4684-879f-1b78451588b2
Failing conversation ID
5cab3be7-b779-42e1-84bb-513aee5da9dc
Windows workspace ID
82ed5a605d7e2b0477fd409854e4f4b1
Windows fsPath
c:\Users\bhsiung\Workdir
Mac workspace ID
534090ab09ce037df9e3b4f4a6724900
Mac fsPath
/Users/bhsiung/Workdir
Cursor version
3.16.17
Error timestamp
2026-08-18 15:24:49 UTC
These are the same logical folder on different OSes. On a Windows-to-Windows migration this works fine because the path hashes match. The Mac path produces a different workspace ID, so all 29 conversations are affected.
Request: Could you please remap / re-associate the conversation blobs stored under workspace 82ed5a605d7e2b0477fd409854e4f4b1 to workspace 534090ab09ce037df9e3b4f4a6724900 on my account? This should restore the ability to resume all my agent conversations on Mac without any data loss.
Happy to provide any additional logs or information. Thank you!
Hi @Bernard_Hsiung Thanks for the post! This is fully recoverable, though the mechanism is a bit different from what you’re picturing. Local agent conversations aren’t stored on our servers, so there’s no server-side namespace for us to remap. Everything, both the conversation list and the message content, lives on your machine in a single SQLite file called state.vscdb. Your conversations are still intact on the Windows side.
That file holds two different kinds of rows. Conversation metadata (titles, IDs, timestamps) is stored as text, while the actual message content is stored as binary blobs. Row-level exports reliably carry the text rows and drop the binary ones, which is exactly the symptom you’re describing: all 29 conversations appear in the sidebar, and every one of them reports missing blobs when you try to resume it.
To recover, quit Cursor on both machines and copy the whole file byte for byte rather than re-exporting it:
A plain file copy preserves the binary rows because nothing is being read and rewritten along the way. As long as the Windows machine or a backup of %APPDATA%\Cursor still exists, nothing is lost.
On the workspace IDs: your observation is correct, those hashes genuinely do differ, but they only name a local directory under User/workspaceStorage// that holds the per-folder sidebar index. The hash is derived from the folder path, so Windows and macOS produce different values for the same logical directory, and that part is expected. It doesn’t affect where conversation content is stored. If you’d also like the sidebar history to line up when you open Workdir on the Mac, open the folder once so Cursor creates the new hash directory, then replace the state.vscdb inside it with the one from the matching Windows directory.
Let me know any follow up questions or concerns and we can take a closer look!
Unfortunately I no longer have the Windows laptop to get the state.vscdb file from, or a backup of it. Next time I’ll take a copy of that instead of an export. I’ll keep the prior conversations as reference and start new ones.