Hey, thanks for the report.
This is a known issue with chat history after updates. The data is usually not lost, it just can’t be read because of a DB glitch.
Try this workaround:
- Fully close Cursor (double-check in Task Manager)
- Open
%APPDATA%\Cursor\User\globalStorage - Find a file named something like
state.vscdb.corrupted.1767... - Rename the current
state.vscdbtostate.vscdb.old - Rename the
.corruptedfile tostate.vscdb - Launch Cursor
More details: Tutorial: How to Fix “Loading Chat” and Recover History
If that doesn’t help, open DevTools (Help → Toggle Developer Tools) and send the console errors. I want to check if this matches other reports from today.