Chats STILL getting lost! Recurring issue!

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chats keep going lost! There are numerous reports about this, and it just keeps recurring! Previous chats just say “Loading chat” and nothing happens.

Steps to Reproduce

It just happens randomly. Open cursor, and it tells you to log in. Browser already picks up that you’re logged in. It then says you can go back to IDE. You do that, and now it gives you a brand new profile. Old chat titles are still visible, but just saying “Loading chat” for all previous chats.

I am so tired of this - so much so that I will NOT renew my annual plan for this product once it is expired!

Expected Behavior

Chat should not go lost!

Operating System

Windows 10/11

Version Information

Version: 2.4.28 (user setup)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known issue. When Cursor forces a re-login, the state database can get corrupted, which makes chat history unreadable. Your data is probably still there, it just can’t be accessed.

Try this to recover your chats:

  1. Fully close Cursor (check Task Manager to make sure the process is really stopped)
  2. Open %APPDATA%\Cursor\User\globalStorage
  3. Look for a file like state.vscdb.corrupted.17xxxxx... (with some numbers)
  4. If you find it, rename the current state.vscdb to something like state.vscdb.backup, then rename the .corrupted file to state.vscdb
  5. Open Cursor again

Full step-by-step guide: Tutorial: How to Fix "Loading Chat" and Recover History (Cursor v2.3.x)

A similar report was fixed this way just a couple of days ago: Lost all cursor settings and chat history for all projects I am working on :-(

For the future, it’s a good idea to regularly back up %APPDATA%\Cursor\User\globalStorage\state.vscdb, especially before updates. The team is aware of this repeating issue, and your report helps us prioritize it.

Let me know if the recovery steps worked.

4

I believe the chatbot @deanrie got it incorrectly. The issue has not been fixed but it was workarounded. In addition the workaround does not work for everybody.

The issue is still there.

5

Oh my word. Now a new upgrade came out yesterday and once again none of my historical chats work. It is ridiculous!

There is a state.vscdb.corrupted file, 13GB in size. Dated 8th February, the date of my report. The newly created state.vscdb file is only 60MB and has not yet been “corrupted” but it is not opening the chat.

Clicking on the chats now does nothing! Not even saying “Loading chat” now - just does nothing. The chat is still listed in the list of chats.

Also, the fix using the “corrupted” file is not applicable here.

WHY guys, WHY? It cannot take THAT long to fix a problem! MULTIPLE versions, MULTIPLE different reasons it seems?

I, like all others, are so tired of this! I am losing time, context and money here.