Hey, thanks for the report. This is a known issue after updating to 2.3.34. Old chats don’t load because of a DB migration problem. Your data is usually not lost, it just can’t be read.
Try this workaround:
- Fully close Cursor (check Task Manager to make sure the process is stopped)
- 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 - Start Cursor
Detailed guide: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x)
If that doesn’t help, open DevTools (Help → Toggle Developer Tools) and send a screenshot of the console errors when you try to open a chat. This will help confirm if it matches other reports from today.