Occasionally the cursor local storage might get corrupted and that leaves undeleatable chats on restart

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Reporting this as a bug because this is the 2nd time in 3 months that I close Cursor and when i re-open i find out that the storage got corrupted

The message have a “Restart” or “Quit” actions, clicking restart allows to get in Cursor and work normally however the layout preferences are resetted and the chats panel breaks with ghost chats that are unrecoverable and some cannot even be removed

image
image1168×1006 10.6 KB

To be fair there are tricks to get rid of those chats like deleting vscode workspace files and tricking cursor in thinking you are opening a new workspace even if is the same folder

However this is a pain in the ass so it would be cool that even if the storage gets corrupted (that should not happen ever) at least ghost chats are not left in a state that cannot even be removed from the UI

Steps to Reproduce

The only thing that can be related that i can think of is that i’ve uninstalled the prettier extension in favor ot oxc, then i restarted cursor and i got the corrupted storage message, in order to make the message go away i had to delete the storage file from the disk

just clicking restart was not enough, i was able to get into the IDE like that but as soon i restarted i got the corruption again, so to fix it permanently i had to start from scratch

I can provide you the corrupted storage file but is 8GB so let me know if you need it i can upload it somewhere hopefully

Operating System

Windows 10/11

Version Information

Version: 2.6.22 (system setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Early Access
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. This is a known issue type. The storage file state.vscdb can grow without limits over time, 8 GB is a good example, and that makes it more likely to get corrupted. When it happens, the chat list and the real chat data can get out of sync, which leaves ghost chats that the UI can’t remove.

The team knows about this. Two recent improvements shipped in recent builds. SQLite WAL mode is now always on, which helps with corruption, and there’s a fix for tombstone row crashes. This should reduce how often it happens, but the root issue of the DB growing without limits is still on our radar.

A couple of things:

  1. You said this happened after uninstalling Prettier and installing oxc. The extension change itself shouldn’t cause corruption, but the restart timing could line up with a write that was still in progress. You didn’t do anything wrong.

  2. Your current workaround of deleting the storage file is the right move when it happens. For reference, the file is at %APPDATA%\Cursor\User\globalStorage\state.vscdb.

  3. Thanks for offering to share the 8 GB corrupted file. If you still have the .corrupted backup file, it could help us debug. You can upload it to a file sharing service and DM me the link.

This report helps us prioritize the fix. Let me know if you hit it again on the latest builds.

7

I can share the link but I cannot write you a DM because Elon Musk wants my money for it, if you can write me first i can probably reply Ray Thurn Void (@raythurnvoid) / X