Hey, thanks for the report. This is a known issue in v2.4.21. After a crash or restart, the auth token can become invalid. That can force a re-login and can break chat loading.
Step 1: Fix chat loading
Sign out and sign back in: Cursor Settings > Sign Out > Sign In. This refreshes your auth token.
Step 2: Try to recover your data
Cursor creates automatic backups, which can help. Here’s how to check:
- Fully close Cursor (confirm in Task Manager)
- Open this folder:
%APPDATA%\Cursor\User\globalStorage - Look for these files:
state.vscdb(current DB, likely corrupted or empty)state.vscdb.backup(automatic backup)state.vscdb.corrupted.XXXXX...(your data marked as corrupted after the crash)
If you found a .corrupted file (best chance to recover):
- Rename
state.vscdbtostate.vscdb.old - Rename the
.corruptedfile tostate.vscdb - Start Cursor
If you only have .backup:
- Rename
state.vscdbtostate.vscdb.old - Rename
state.vscdb.backuptostate.vscdb - Start Cursor
There’s also a detailed tutorial with a PowerShell script that automates this process: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x)
To prevent this in the future:
Periodically back up these paths:
%APPDATA%\Cursor\User\globalStorage\state.vscdb%APPDATA%\Cursor\User\workspaceStorage
By the way, how much free disk space do you have? Low free space can trigger issues like this.
Let me know which files you found in that folder and whether you were able to recover anything.