Hey, this is a known issue in versions 2.3.34 to 2.3.35. Your data usually isn’t lost, it just can’t be read because of a DB issue.
Try this workaround:
- Fully close Cursor (check Task Manager to make sure the process isn’t running)
- Open
%APPDATA%\Cursor\User\globalStorage - Find a file like
state.vscdb.corrupted.1767... - Rename the current
state.vscdbtostate.vscdb.old - Rename the
.corruptedfile tostate.vscdb - Launch Cursor
Full instructions: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x)
If it doesn’t help, open DevTools (Help → Toggle Developer Tools) and share a screenshot of the console errors. Also, can you create new chats, or is nothing working at all?