🚫 Cursor "Loading Chat" Infinite Loop Fix — Delete state.vscdb in Workspace Folder
Are you stuck in an endless "Loading Chat" loop in Cursor after a project update or reopening an old project? You're not alone. Many developers have reported that Cursor gets stuck in an unresponsive chat window due to corrupted workspace state files — but here's a quick and effective fix.
🛠️ Problem: Cursor Chat Stuck on "Loading..."
When you open a project in Cursor, the Chat panel freezes indefinitely, showing "Loading Chat..." and becoming completely unresponsive.
This often happens after:
A Cursor update
Loading a project with a large or corrupted chat history
Migrating a project from one machine to another
✅ Solution: Delete state.vscdb in the Workspace Storage Folder
To fix this issue, follow these simple steps:
🔍 1. Locate the Workspace Storage Folder
plaintext
C:\Users\
You will see a list of random-looking folders, each corresponding to a different project.
🧼 2. Find the Affected Project
Open one of these folders and look for a file named:
state.vscdb
To identify the correct one, you can sort the folders by "Date Modified" or open each and check for familiar files like workspace.json.
🗑️ 3. Delete state.vscdb
Once you find the right folder, delete the state.vscdb file.
Optionally, also delete state.vscdb.backup if it exists.
🔄 4. Relaunch Cursor
Open Cursor again and re-open your project — the Chat should now load normally.
🧠 Why This Works
state.vscdb is a lightweight SQLite database used by Cursor (and VSCode) to manage the internal workspace state, including chat UI persistence. When this file is corrupted or overloaded, the chat panel may freeze while trying to load its previous session.
🔎 Keywords for Developers
To help others find this solution, here are some useful long-tail keywords:
cursor chat stuck on loading fix
cursor endless chat loading issue
cursor ai chat panel not responding
how to fix state.vscdb file in cursor
cursor chat freeze after update
cursor workspaceStorage bug fix
cursor stuck loading chat solution 2025
💬 Final Notes
This bug has been confirmed by users on the Cursor Community Forum and Reddit. Until an official patch is released, this manual cleanup is the best workaround.
Have more issues with Cursor? Drop a comment or share your own fix — let’s help each other code better!
