Chat History Wiped AGAIN!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

For the second time you have managed to reset my state.vscdb with your unstable, buggy software!
I had cursor open on version 2.3.29.
I’ve closed it down 10 minutes ago and opened a new copy and old chats stick on Loading Chat…

I’ve browsed to the globalStorage folder and I see a 4KB file

Steps to Reproduce

Use cursor for a few days/weeks and it resets your state.vscdb that has been reported by hundreds of others and you claimed was fixed in version 2.3

What a joke!

Expected Behavior

Stop wiping people’s chat history.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29 (user setup)
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. Your data can definitely be recovered.

You have a file named state.vscdb.corrupted.1767892516529 that’s 2.3 GB. That’s your full chat history. Your current state.vscdb is only 4 KB, so it’s empty or reset.

Steps to restore:

  1. Fully close Cursor (double-check in Task Manager).
  2. In %APPDATA%\Cursor\User\globalStorage:
    • Rename state.vscdb to state.vscdb.broken
    • Rename state.vscdb.corrupted.1767892516529 to state.vscdb
  3. Launch Cursor.

Your chat history should come back. Let me know if it worked.

So what is the point of a .backup file if Cursor doesn’t detect it has corrupted the primary file and restore from the backup?
Why would I have any confidence in swapping back to a file that has been labelled “.corrupted” ?

Is this really what to expect from a fairly expensive $200 per month subscription that it periodically corrupts chat history and it’s down to the end user to fix the mess?

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.