The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
Request ID: 49f21fc5-7ab8-4cd1-8fce-2451a9c91f21
{“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 uLw (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44320:28201)
at mKd.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44320:32965)
at async yvf._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47670:4084)
at async yvf.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47670:7354)
at async yvf.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47670:19276)
at async Vut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36386:16963)
at async Object.Fs [as onSubmit] (vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46675:3887)
at async vscode-file://vscode-app/c:/Users/conno/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45736:103088
Hey, this is a known issue with extension host startup on Windows. Most often it happens because the cursor-socket extension is missing the out\ folder, and this fix is usually reliable.
Since you’re using the user setup, open PowerShell as Administrator and check what’s inside:
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
If you see a dist\ folder but no out\, copy it over. A copy tends to survive reboots better than a symlink:
Then fully quit Cursor. In Task Manager, make sure there’s no Cursor.exe left, then start Cursor again.
If the folder looks different, or this didn’t help, try these in order:
Clear cache: close Cursor, delete %APPDATA%\Cursor\CachedData, %APPDATA%\Cursor\Cache, %APPDATA%\Cursor\GPUCache, then start it again.
Run cursor --disable-extensions. If it works like that, an extension is blocking the extension host.
If you use antivirus or endpoint protection, add the Cursor folder to exclusions. That’s a common reason why out\ disappears.
Note: Cursor auto-updates might remove out\ again, so you may need to repeat the Copy-Item step. A permanent fix on our side is in progress, but I can’t share an ETA yet.
If none of this worked, send the output of the first command dir ... and we’ll dig in further.
Thanks for the logs. I can see out\ is back in place, so the copy worked, but the issue is still there. Let’s narrow down the cause.
When you run cursor --disable-extensions, please actually try sending a prompt to the agent in that mode. Does it work, or do you get the same error? This is the most important check. If the agent works with extensions disabled, then some third-party extension is blocking it.
Do you have an antivirus or endpoint protection tool running like Defender, or a corporate EDR? This is a common cause on Windows. AV can kill the extension host or delete the out\ folder. Add the whole install folder to exclusions:
%LOCALAPPDATA%\Programs\cursor
After that, fully close Cursor, and check in Task Manager that Cursor.exe is not still running, then start it again.
Check workspace trust. Open a brand new empty folder and try there. If the agent works in an empty folder, the problem is related to trust or settings in that specific project.
Between attempts, always fully quit Cursor via Task Manager. Otherwise an old process can interfere.
A permanent fix on our side is in progress, but I can’t share an ETA yet. Let me know what you see in step 1, running with --disable-extensions, since the next steps depend on that.