The Cursor Extension Host completely stalls during startup, which prevents AI agents, source control, and all extensions from loading. The issue persists across standard cache wipes and running with disabled extensions. Performing a hard reset by deleting the ~/.cursor directory temporarily resolves the issue, but the host eventually degrades and fails again after a short period of use in the workspace.
Steps to Reproduce
Open Cursor and load the affected workspace.
Wait for the editor to initialize.
Observe the AI Agent panel and Source Control tab.
Open Developer Tools and review the Extension Host and Console logs.
Expected Behavior
The extension host initializes successfully within a few seconds. Source control registers the git repository and AI agents are fully responsive.
workbench.desktop.main.js:46036 [TerminalExecutionServiceProxy] v3 health check failed after 6838ms: Error: Extension host not ready after 10 attempts (6838ms elapsed)
at mVd._createSessionWithRetry (workbench.desktop.main.js:46036:6255)
at async mVd._healthCheckV3 (workbench.desktop.main.js:46036:4933)
at async mVd._initializeDelegate (workbench.desktop.main.js:46036:9503)
workbench.desktop.main.js:41157 [auth] BackendClient proceeding without auth ready (timeout or logged out)
Object
workbench.desktop.main.js:41157 [auth] Timeout waiting for auth ready signal
Error: No Connect transport provider registered.
at eWa.transport (workbench.desktop.main.js:28821:110960)
at async O1.createSingleServer (workbench.desktop.main.js:28821:112552)
at async O1.get (workbench.desktop.main.js:28821:111758)
at async gGd.forceRefreshServerConfig (workbench.desktop.main.js:45780:44024)
setTimeout
e.setTimeout @ workbench.desktop.main.js:40548
(anonymous) @ workbench.desktop.main.js:28821
transport @ workbench.desktop.main.js:28821
workbench.desktop.main.js:41329 Failed to flush analytics events: Error: No Connect transport provider registered.
at eWa.transport (workbench.desktop.main.js:28821:110960)
at async O1.createSingleServer (workbench.desktop.main.js:28821:112552)
at async O1.get (workbench.desktop.main.js:28821:111758)
at async nxd.flushAll (workbench.desktop.main.js:41329:937)
at async workbench.desktop.main.js:41329:624
flushAll @ workbench.desktop.main.js:41329
workbench.desktop.main.js:28918 [PluginsProviderService] Timed out waiting for plugins provider after 30000ms
_warnProviderWaitTimeout @ workbench.desktop.main.js:28918
(anonymous) @ workbench.desktop.main.js:28918
(anonymous) @ workbench.desktop.main.js:60
setTimeout
e.setTimeout @ workbench.desktop.main.js:40548
fq @ workbench.desktop.main.js:60
_callWithTimeout @ workbench.desktop.main.js:28918
getPluginCommands @ workbench.desktop.main.js:28918
loadPluginCommands @ workbench.desktop.main.js:45762
loadAllCommands @ workbench.desktop.main.js:45762
setTimeout
e.setTimeout @ workbench.desktop.main.js:40548
(anonymous) @ workbench.desktop.main.js:28821
transport @ workbench.desktop.main.js:28821
workbench.desktop.main.js:65 ERR No Connect transport provider registered.: Error: No Connect transport provider registered.
at eWa.transport (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28821:110960)
at async O1.createSingleServer (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28821:112552) Error: No Connect transport provider registered.
at eWa.transport (workbench.desktop.main.js:28821:110960)
at async O1.createSingleServer (workbench.desktop.main.js:28821:112552)
Hey Nikola, thanks for the detailed report with logs, it really helps. Both messages Extension host not ready after 10 attempts and Timeout waiting for auth ready signal are downstream symptoms that the Extension Host isn’t starting in time. This is a known issue on our side, and it looks like corrupted workspace storage state.
Delete the folder for the specific workspace from this path and make a backup first:
~/.config/Cursor/User/workspaceStorage/
The subfolders have hash-like names. You can find the right one by running grep on workspace.json for your project path, or just delete them all if there aren’t many.
Start Cursor again and open the project.
If it comes back, I’d like to understand the trigger. Did you notice any pattern, for example:
Does it happen after specific actions like a big chat, lots of terminals, or reloading the window?
Does it line up with opening or closing a specific extension or MCP server?
Do you see anything in the Extension Host logs Output > Extension Host right before it stops responding?
We’re tracking the issue, but I can’t share an ETA for a fix yet. If there are updates, I’ll reply in the thread.
