Chat stuck on “Loading Chat” – chat history / summaries not loading

[AlBarzi]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

The Cursor chat is permanently stuck on “Loading Chat”.
Because of this, I cannot see the active chat OR my chat history/summaries.

This blocks access to all previous conversations and prevents starting new chats.

Steps to Reproduce

1. Open Cursor
2. Open the Chat panel
3. The chat remains stuck on “Loading Chat”
4. Chat history/summaries never load

This happens consistently on my office network.
On a mobile hotspot, diagnostics pass, but the UI can still remain stuck.

Expected Behavior

The chat should load normally and display the chat history/summaries.
If streaming fails, the UI should recover or fall back instead of staying stuck in a loading state.

Operating System

Windows 10/11

Version Information

IDE: Cursor (latest version as of today)
CLI: 2026.01.17-d239e66

For AI issues: which model did you use?

Multiple models (GPT and Claude). Issue occurs regardless of model.

Additional Information

Network diagnostics show SSE / streaming responses being buffered by a proxy on the office network.
Cursor support has already escalated this issue internally.

This appears to be a UI state issue where the chat interface does not recover properly when streaming fails.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This is a known issue after updating to 2.3.34+. Chats are stored locally, and “Loading Chat” means Cursor can’t read the database.

Usually the data isn’t lost. The file just gets marked as corrupted. Try this:

• Fully quit Cursor (also check Task Manager)
• Open %APPDATA%\Cursor\User\globalStorage
• Look for a file like state.vscdb.corrupted.1767... (the numbers will be different)
• Rename the current state.vscdb to state.vscdb.old
• Rename the .corrupted file to state.vscdb
• Start Cursor

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

If there are no .corrupted files, open DevTools (Help > Toggle Developer Tools), try opening a chat, and send a screenshot of the Console errors. That will help narrow down what broke.

A network proxy is most likely not related. The history loads from a local DB, not over the network.