Loading chat forever

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Many of my project directories have agent chat histories that cannot be opened at all and remain stuck on “Loading chat.” Some working directories even show a black screen after being opened.

I have never encountered this issue before. When testing the network connection, the results are inconsistent: sometimes the chat and agent connection tests fail, while other times they pass. Local service checks on my side show no issues.

I am currently waiting for the ports / connections to be restored to normal.

Steps to Reproduce

I believe this may have happened when I opened one folder and then, within the same workspace, selected and opened another folder. After that, the issue started occurring. I’m not sure whether this was caused by my actions or by an underlying issue in the tool itself.

Expected Behavior

I would like all agent conversation lists in my folders to be visible, and the full conversation history to be accessible. Not only Loading chat

Screenshots / Screen Recordings

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

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. This is a known issue after updating to 2.3.34. Old chats don’t load because of a DB migration problem. Your data is usually not lost, it just can’t be read.

Try this workaround:

  1. Fully close Cursor (check Task Manager to make sure the process is stopped)
  2. Open %APPDATA%\Cursor\User\globalStorage
  3. Find a file like state.vscdb.corrupted.1767...
  4. Rename the current state.vscdb to state.vscdb.old
  5. Rename the .corrupted file to state.vscdb
  6. Start Cursor

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

If that doesn’t help, open DevTools (Help → Toggle Developer Tools) and send a screenshot of the console errors when you try to open a chat. This will help confirm if it matches other reports from today.

2 Likes

Thank you very much. With this operation, my agent chat history has been restored. However, I now have an issue where some directories cannot be opened (they feel like they’re corrupted). After selecting them, the screen just turns black (as shown in the screenshot, with a faint split-pane background color). After closing and reopening the app, it remains black. Most other directories work fine. These directories that can’t be opened seem to be a few of my last working directories.

What should I do? Thank you very much.

Thank you very much. I still have the following issue(s).

Then I ran more tests and found that after logging out and back in several times, I’m prompted to log in ag

ain. After that, the old records you asked me to modify are gone, and I have to restore them again from the backup.

The black screen in certain directories is a separate issue from “Loading Chat.” It’s caused by a corrupted state.vscdb, but this time it’s in workspaceStorage (not globalStorage).

Try this workaround for the affected directories:

  1. Close Cursor completely
  2. Go to %AppData%\Cursor\User\workspaceStorage\
  3. You’ll see lots of folders with hash-like names. Open workspace.json in each one and find the one that points to the affected directory
  4. In that folder, rename state.vscdb to state.vscdb.bak
  5. Open Cursor and then open that directory. A new state.vscdb should be created

Unfortunately, this will reset the chat history for that directory.

About losing history after logout and login, that’s odd. Can you confirm:

  • After logging out and back in, are you opening the same folder as before?
  • Are you logging out via Cursor Settings, or somewhere else?

Also, did you use “Open Chat as Editor”? Right now it can cause this exact black screen issue. The team knows about it and is working on a fix.

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