Hey, this is a known issue with extension host initialization on Windows. The team is aware, but there’s no ETA yet.
Try this:
Clear Cursor cache:
Fully close Cursor
Delete these folders: %APPDATA%\Cursor\CachedData, %APPDATA%\Cursor\Cache, %APPDATA%\Cursor\GPUCache
Start Cursor again
If that didn’t help, check extensions. Start Cursor from the command line with cursor --disable-extensions. If it works, an extension is blocking the extension host. You can enable Extension Monitor in Settings > Application > Experimental > Extension Monitor Enabled, then open it via Cmd+Shift+P > Developer: Open Extension Monitor to see what’s slowing it down.
Last resort, reset user data: rename %APPDATA%\Cursor to Cursor_backup and start Cursor again. Cursor will create a fresh config.
Also, if you’re using an antivirus or VPN, try turning it off temporarily and test again.
I can see the standard steps didn’t help, and it works on another computer on the same network. That points to a local issue with the cursor-socket extension.
Try this. Open PowerShell as admin and check what’s inside the cursor-socket folder:
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
If you see a dist\ folder but no out\, create a symlink:
cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
New-Item -ItemType SymbolicLink -Name "out" -Target "dist"
Then restart Cursor.
The team is aware of this issue on Windows and is tracking it. Let me know if the symlink fixes it.
Request ID: 99a58da8-318f-49c4-b2ce-faf142820148
{“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 vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:27166
at async RlS.createExecInstance (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:23636)
at async EF_ (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28640:630571)
at async BF.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28861:7896)
at async Wpd.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:1792)
at async vHS.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41234:4969)
at async Dkd.buildComposerRequestContext (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:4190)
at async Dkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:6959)
at async Dkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:17740)
at async F3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28972:16809)
at async Object.La [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40227:4231)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40226:100561
Steps to Reproduce
Request ID: 99a58da8-318f-49c4-b2ce-faf142820148
{“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 vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:27166
at async RlS.createExecInstance (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:23636)
at async EF_ (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28640:630571)
at async BF.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28861:7896)
at async Wpd.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38239:1792)
at async vHS.execute (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41234:4969)
at async Dkd.buildComposerRequestContext (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:4190)
at async Dkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:6959)
at async Dkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41244:17740)
at async F3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28972:16809)
at async Object.La [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40227:4231)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40226:100561
@sdfy, this is the same cursor-socket issue we fixed earlier in the thread, but you’re using the system setup so the path is different. Open PowerShell as admin and check what’s in this folder:
dir "C:\Program Files\Cursor\resources\app\extensions\cursor-socket"
If you see dist\ but there’s no out\, create a symlink:
cd "C:\Program Files\Cursor\resources\app\extensions\cursor-socket"
New-Item -ItemType SymbolicLink -Name "out" -Target "dist"
Then restart Cursor.
If the folder looks different or the symlink didn’t help, paste the output of the first command and we’ll figure it out. This is a known Windows bug and there’s no fix timeline yet.
When is this issue going to be properly resolved? I opened two projects—the first one works fine, but the second one doesn’t. What’s the problem here? You’ve been investigating this for so long and still haven’t fixed it?
@yang_zhenfang Cursor most likely updated after the symlink worked last time, and the update overwrote the extension folder. The symlink is gone, so we’re back to the same issue. This can happen on Windows until they ship a permanent fix. I can’t share an ETA yet, but the issue is being tracked.
Please check the same folder in PowerShell as admin and recreate the symlink. First, confirm which install you have, user setup or system setup:
User setup (if you installed for the current user):
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
System setup (if you installed for all users on the machine):
dir "C:\Program Files\Cursor\resources\app\extensions\cursor-socket"
If you see dist\ but no out\, recreate the symlink, example for user setup:
cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
New-Item -ItemType SymbolicLink -Name "out" -Target "dist"
After that, fully quit Cursor and start it again. Let me know if it didn’t help or if the folder looks different. Please paste the output of the first command.
About one project working and another not working, it’s probably a side effect of the same bug. If the extension host didn’t start correctly, one window might have cached it, but a new window won’t pick it up. After the symlink and restart, both should work.
Hey, before doing a full reinstall, try a more durable workaround. The symlink can get wiped by Cursor updates or some antivirus tools. Copy the folder instead. It tends to survive reboots better.
Then fully quit Cursor and start it again. Note: if Cursor auto-updates, the out\ folder will likely need to be recreated. If you have antivirus running, please add the cursor folder to its exclusion list. That may be why the symlink disappeared on reboot.
If you still want a clean reinstall, here’s the full procedure for user setup:
Fully quit Cursor. Check Task Manager for any leftover Cursor.exe
Uninstall via Windows Settings > Apps > Installed apps > Cursor > Uninstall
Heads up: a reinstall doesn’t guarantee a fix, since the missing out\ folder is a packaging issue affecting some Windows installs. If it still happens after reinstall, the Copy-Item step above is the workaround until the team ships a permanent fix. No ETA on that yet.
Let me know which path you took and whether it stuck after a reboot.
Glad to hear it’s working again. But keep in mind this is the same packaging issue, so if Cursor auto-updates or some cleanup tool deletes the out\ folder, the timeout may come back.
If that happens, a more reliable workaround is to copy the folder instead of creating a symlink, from post #19:
After that, fully quit Cursor and start it again. It’s also worth adding the Cursor folder to your antivirus exclusions, since in some cases the antivirus deletes the out\ directory after a reboot.
We’re still working on the proper fix, but we don’t have an ETA yet. If the issue comes back, please bump the thread again or message me.
hi sorry to comment on this i seem to be battling this same issue on my mac, i do not have a vpn running i cleared cache, uninstalled and reinstalled even downgraded my ide. still to no avail my idea is showing upgrade to pro, even though i am already on pro. when i prompt i get the agenout error as everyone here
HI,I meet similar problem,but I can’t solve it use the way above.I’m using ssh and corporate VPNs.I can use models locally but agent execution timed out on the ssh serve
unfortunately i am using the ide, althought the options above did actually remove the upgrade to pro that i have been seeing on my ide, i still cant prompt
