I am seeing an issue with historical chat loading after enabling VS Code Settings Sync, and I would like to confirm whether this is expected behavior or a known limitation.
Symptoms
Chat titles appear in the Cursor chat sidebar.
Clicking an older chat does not load any chat content.
New chats work normally.
This began immediately after enabling VS Code Settings Sync which triggered a re-authention in Cursor.
What I have confirmed
New and historical chat content exists as plain-text transcript files under:
C:\Users.cursor\projects\agent-transcripts\
Image assets for older chats exist under the current workspace storage location:
C:\Users\AppData\Roaming\Cursor\User\workspaceStorage\images
New images generated in chats are being saved under the legacy project assets path:
C:\Users.cursor\projects\assets
These new image files are named using an encoded absolute path that references the current workspaceStorage location, for example:
c__Users__AppData_Roaming_Cursor_User_workspaceStorage_7244fd071cc555533a1614903e6_images_image-61aa103a-d890-4772-1111-ad2ab8525cdc.png
The full console log from initial open of cursor was quite long with many errors and too large for this portal. I will have to send it another way if you need it.
I see the same bug from Can't load or click on chats - the error handleDeselectingComposer + corrupted database.
Good news: the data is not lost, the transcript files in .cursor/projects/agent-transcripts are intact. The database just got corrupted.
Try to restore access:
Close Cursor completely (check in Task Manager)
Open %APPDATA%\Cursor\User\globalStorage
I see in the screenshot state.vscdb.corrupted.1769921712534
Rename the current state.vscdb and state.vscdb.backup to something like state.vscdb.old
Rename state.vscdb.corrupted.1769921712534 back to state.vscdb
Launch Cursor
This should restore access to the chats. If it doesn’t work, show me the exact size of state.vscdb (right-click - Properties - Size), and we’ll try another option.
About Settings Sync: it’s a trigger, but not the cause. The corrupted file appeared due to a crash while writing to the database.
Awesome, the chats now load in. There a are a few recent chats that don’t but that’s not an issue for me as they were small tasks. There are still many errors and warnings in the Cursor console.
Do you think my Cursor setup could be potentially unstable and/or susceptible to having problems with future updates? I have had issues for quite a while with Cursor updates failing.
Do you have any suggestions on how to get a fresh install while preserving all my settings?