I solve this by rollback the version to 2.3, at cost of losing all the conversation. Do not update to version 2.4 unless they have fixxed the instability issue.
Hey, thanks for the report. This is a known issue with the 2,4.x update, you’re not the only one. There have been dozens of similar reports over the last few days. The team is aware, and the bug is logged.
Rolling back to 2,3 is the right move to get things working again. About the chats, the data is probably not lost. It’s more likely the DB can’t read it after the rollback.
Try this to recover:
Fully close Cursor (double check in Task Manager)
Open %APPDATA%\Cursor\User\globalStorage
Do you see files like state.vscdb.corrupted.1767...?
Hi, thanks for the kind response. Here is what the target folder shows, and there is no files with corrupted.{id} inside. Please take a look and help if you can restore the history chat. Although I can start a new chat to teach AI the old stuff but with recovered chat it would be much more effortless. Thanks.