Hey, thanks for the report. This is a known issue after updating to versions 2.3.34+. Usually chat won’t load because the database is corrupted, but your data isn’t lost, it’s just not readable.
Try this workaround:
Fully close Cursor (check Task Manager to make sure the process is stopped)
Open %APPDATA%\Cursor\User\workspaceStorage
Find the folder for your current project (each one has a workspace.json with the project path)
Rename state.vscdb to state.vscdb.bak
Start Cursor
This will delete the chat history for that project, but it should make chats open again.
Thanks for the update, appreciate it. I truely want to cry rn it’s ahrd to imagine i’ve lost it all…
There no corrupted file that’s why I find it really odd.
Looks like you checked the workspaceStorage folder, but .corrupted files are more often in a different folder, globalStorage.
Try this:
Fully close Cursor (check in Task Manager)
Open %APPDATA%\Cursor\User\globalStorage
See if there are files like state.vscdb.corrupted.1767... (the number will be different)
If yes, rename it to state.vscdb (you can temporarily move the old state.vscdb and state.vscdb.backup into a separate folder)
If there are no corrupted files in globalStorage either, send a screenshot of what’s inside both folders (workspaceStorage and globalStorage) and we’ll take a look.
In that case, the next thing to check is workspaceStorage. There are folders with different dates there (21/12, 26/12, 08/01, etc.). If the issue is only in one specific project, the data might be there:
Open %APPDATA%\Cursor\User\workspaceStorage
Find the folder for the project you need. Inside each one there’s a workspace.json with the path
Check if there’s a state.vscdb.backup with an older date
If everything has recent dates and there are no backups, the data most likely wasn’t saved. This is a known issue in 2.3.34+ where, if the DB gets corrupted, the recovery files don’t get created correctly.
Can you also check Developer Tools Console and see what errors you get when you try to open the chat? At least we’ll know what exactly is breaking.
Thanks for the help.
Nothing happens, I tried the Recorder, Network but it’s like cursor do not register anything at all.
I don’t know if it’s related or not but now I have this error when I try to apply changes, I don’t want to lose all a second time haha. Failed to apply worktree to current branch: Unable to read file ‘###\scripts\deep_audit.py’ (Error: Unable to resolve nonexistent file ‘####\kyy\scripts\deep_audit.py’)
I just payed the 212 euros plan to help me but it starts to get a bit worrying
Thanks for the extra info. If Developer Tools doesn’t show anything when you click on a chat, try this:
Open the chat panel
Press CMD+Shift+P, then choose Developer: Toggle Developer Tools
Go to the Console tab
Click any chat from your history
Send a screenshot of any errors (red messages) if they show up
About the worktree error (“Unable to read file”), that’s a separate bug. Can you share the full error text? It looks like the agent is trying to apply changes to a file that was deleted or renamed during the session.
when I click on the chat I want to open, and I insist on thanking you again for the help.
workbench.desktop.main.js:13003 [composer] No composer data handle found [handleDeselectingComposer]
Great, the No composer data handle found error is exactly what we needed to see. This is a known issue in 2.3.x, and the team is aware.
Since the usual fixes for corrupted files didn’t work, try this instead:
Export your profile.
Fully close Cursor (double-check in Task Manager).
Open %APPDATA%\Cursor\User\globalStorage.
Find state.vscdb and rename it to state.vscdb.old.
Start Cursor.
Go through the Cursor setup again and import your profile.
This should reset the global chat state.
About the worktree error (“Unable to read file”), that’s a separate bug. It happens when the agent tries to apply changes to a file that was deleted or renamed during the session. Usually it helps to start a new chat and avoid renaming or deleting files while the agent is working.
Let me know if the globalStorage workaround helped.
This does not work, I’ve lost my new chat now I’m gonna cry I re-did everything yesterday after the loss this is non-sense… Can you help? Is there any way to retrieve the data?
Sorry but I’m getting a bit emotionnal to be honest.
workbench.desktop.main.js:13003 [composer] No composer data handle found [handleDeselectingComposer]
