2.3.34 fully breaks looking back to older chats

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I absolutely cannot restore archived chats, or load any chats before Jan 12. Tried restarting several times, chats just won’t load.

Steps to Reproduce

Have archived chats pre-2.3.34
Try starting 1 new chat
Try loading an older chat, or archived chat
Note loading state never stops

Expected Behavior

Load any chat, new or old, at any time for any reason.

Screenshots / Screen Recordings

Screenshot 2026-01-12 085053.png
Screenshot 2026-01-12 085053.png1028×746 26.9 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
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

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Tried to upload a gif showing some new behavior but apparently you won’t let me upload more than 5MB, so ■■■■ me then I guess. Thanks. :+1: Love seeing what $800/mo gets me.

4

Hey, thanks for the report.

This is a known issue with chat history after updates. The data is usually not lost, it just can’t be read because of a DB glitch.

Try this workaround:

  1. Fully close Cursor (double-check in Task Manager)
  2. Open %APPDATA%\Cursor\User\globalStorage
  3. Find a file named something like state.vscdb.corrupted.1767...
  4. Rename the current state.vscdb to state.vscdb.old
  5. Rename the .corrupted file to state.vscdb
  6. Launch Cursor

More details: Tutorial: How to Fix “Loading Chat” and Recover History

If that doesn’t help, open DevTools (Help → Toggle Developer Tools) and send the console errors. I want to check if this matches other reports from today.

5

That doesn’t feel very robust. If this is a known issue, surly you could write a script that actions this. I really have to do this everytime Cursor decided to push an update?

6

I’m a bit surprised that this is the proposed solution. Manually correcting something that should be handled automatically by Cursor doesn’t seem acceptable.

This behavior is broken, and it’s still present in version 2.4.5. Could you please address and properly fix this issue?

7

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