Updating to the latest version caused some conversations to be lost

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to this version, I found that the sidebar chat was missing, and these were all very large chats—chaps that involved changes to hundreds of code files at once—and these chats were from just a few hours before the update.

Steps to Reproduce

You might need to try making hundreds of changes to the model in one go within a single dialogue, then update to this version; you’ll find that the dialogue is missing.

Operating System

Windows 10/11

Version Information

Version: 2.6.14 (user setup)
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.28000

For AI issues: which model did you use?

gpt5.4

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, this is a known issue. Large chats, especially ones with hundreds of file changes, are more likely to hit this after updates. Your data is probably still there, it’s just not accessible in the UI.

Here’s what to try:

  1. Close Cursor completely (check Task Manager too).
  2. Open %APPDATA%\Cursor\User\globalStorage
  3. Look for files named state.vscdb.corrupted.1741... (the number will be different).
  4. If you find one, rename the current state.vscdb to something like state.vscdb.old, then rename the .corrupted file to state.vscdb.
  5. Relaunch Cursor.

Detailed tutorial here: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x)

If there are no .corrupted files, there’s a more advanced recovery approach using Python scripts to manually restore the sidebar index. A community member documented it here: How I Recovered my "Vanished Cursor Chat" - so you dont have to

Also, make sure to update to v2.6.16 or later when it’s available for you. It includes a fix specifically for large conversations with many file changes.

The team is aware of this class of issues. Let me know if the workaround helps or if you need more guidance.

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