2 issues, one is ofc the extension host issue, where this time the whole workspace is disconnected, and can’t keep a stable connection.
But the second issue is how i keep having to delete state.vscdb from C:\Users\USER\AppData\Roaming\Cursor\User\globalStorage
This deletes the whole agent chats…
Because they become “corrupt”.
Steps to Reproduce
Make a big plan.
Execute the plan.
If the plan is way too big, it will crash/lag out the whole background processes and extension host, making sure i have to clear the whole state.vscdb again.
Expected Behavior
Perhaps find a way to store the chats in github or something by default, instead of being deleted or even being corrupt?
For AI issues: add Request ID with privacy disabled
Request ID: 31399bb6-73b8-4d66-a0a7-2dec4d9f9961
{“error”:“ERROR_EXTENSION_HOST_TIMEOUT”,“details”:{“title”:“Workspace Disconnected”,“detail”:“Cursor lost connection to the workspace while starting tool execution. Reload the window and try again.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:,“planChoices”:}}
Workspace Disconnected Cursor lost connection to the workspace while starting tool execution. Reload the window and try again.
L7t: Workspace Disconnected Cursor lost connection to the workspace while starting tool execution. Reload the window and try again.
at Rw1 (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:27561)
at kog (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:26375)
at qw1 (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:7469)
at Pog.run (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:12367)
at async Ule.resume (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48124:7159)
at async M7g.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48195:12809)
at async M7g.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48195:21573)
at async sut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35854:1949)
Most important thing first: please stop deleting state.vscdb. When Cursor flags the database as “corrupt” after a crash, your conversations are usually still inside it. Cursor doesn’t wipe the file, it renames it to state.vscdb.corrupted.<timestamp> and starts a fresh one, so an empty sidebar is often just a truncated index rather than lost data. Deleting the file is what makes the loss permanent.
If it happens again:
Back up the whole globalStorage folder first (copy it somewhere safe) before touching anything.
Keep any state.vscdb.corrupted.<timestamp> and state.vscdb.backup files. Those are your recovery source, and the conversation data usually still lives there.
For the “Workspace Disconnected” / disconnect error:
Open the Command Palette (Ctrl+Shift+P) and run Developer: Restart Extension Host. That re-establishes the agent connection more reliably than a full reload and usually clears it without restarting Cursor.
If it’s frequent, launch cursor --disable-extensions to test. If it’s stable that way, re-enable extensions one at a time to find a heavy one.
On Windows, adding Cursor to your antivirus/EDR exclusion list often helps, since real-time scanning can slow the extension host enough to trip the timeout. Exclude the Cursor install folder, your project folders, and C:\Users\<you>\.cursor\.
To reduce how often this happens:
Close Cursor gracefully (File > Exit) before Windows restarts or installs updates. The chat loss is tied to ungraceful shutdowns after long sessions.
Keep the database from growing too large, which contributes to the crashes: periodically run Developer: Delete Old Chats (note: this removes chats older than the window you pick, so choose a range you’re comfortable with) and Developer: GC Agent KV Blobs from the Command Palette.
Breaking very large plans into smaller agent runs reduces the memory spike that triggers the disconnect.
On storing chats in GitHub: chat history lives in a local database today, so there’s no built-in sync, but I’ll pass that suggestion along as feedback.
I tried this now, because ALL of my agents just disconnect.
Request ID: 349bffaa-8609-4db4-adfb-73b08938bcfa
{"error":"ERROR_EXTENSION_HOST_TIMEOUT","details":{"title":"Agent Execution Timed Out","detail":"The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.","isRetryable":false,"shouldShowImmediateError":true,"additionalInfo":{},"buttons":[{"label":"Reload Window","reloadWindow":{}}],"planChoices":[]}}
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at CDy (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12158:32671)
at e2r.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12158:37713)
at async Lkh._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:4071)
at async DIe (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11913:12018)
at async vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:8088
at async DIe (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11913:12018)
at async Lkh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:8012)
at async Lkh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:22888)
at async IRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12142:2399)
at async Object.du [as onSubmit] (vscode-file://vscode-app/c:/Users/0000/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:23548:34996)
Since you posted, we’ve made significant changes to how chat history is stored, which should make chats much more resilient to crashes and unexpected shutdowns. You’re on 3.7.27, and these changes landed in later versions.
Give us a shout if you’re still facing any issues.
Hello again.
Yes, the chat history works now.
But i have noticed that if context history hits max, it becomes really slow.
Earlier, I thought it would make a new chat once it hits max and reference the old chat, that way, it can continue faster.