Installed last update, evening of 1/21/26. Immediately on restart, every LLM interaction is met with “Waiting for extension host”, then an error message “Agent execution timed out - The agent execution provider did not respond within 16 seconds. This may indicate the extension host is not running or is unresponsive”. No model works in any mode (agent, ask, etc). I have tried disabling ALL extensions, makes no difference. Restart / reboot does not help. My internet access works fine.
Steps to Reproduce
After installing update, the bug happens every time
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.4.14
VSCode version: 1.105.1
For AI issues: which model did you use?
All models including Gemini 3 Pro, GPT 5.2, Claude Opus 4.5
For AI issues: add Request ID with privacy disabled
Request ID: 34e27121-3060-40d3-86d7-631c4487556b
{“error”:“ERROR_CUSTOM”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond within 16 seconds. 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:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:8256
at async WHf.createExecInstance (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async YNg (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async wW.execute (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async r1a.execute (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async gcb.execute (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34229:14275)
at async Wpc.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:3573)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:5171)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Oi (vscode-file://vscode-app/c:/Users/Jim/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
I have been installing the early accesss updates, yesterday the 2.4.5 update was having issues with agent executed commands instantly being cancelled and shell commands failing to generate, right now its on 2.4.7 and that fixed all my issues, it’s prompting another update right now but I’d recommend turning on beta updates and seeing if that fixes it.
In that time are Rules and Skills processing. Even if you dont have specific skill you can have enabled Include third party. For me works this .. wait about 30-60s … do not RELOAD. Just close popup and after some time (you can check Rules and Skills are loaded) just retry you prompt.
I’m on 2.4.28 and having this problem (all LLM interactions hanging on “Waiting for extension host” and then erroring after 16 seconds).
It started after I updated yesterday. I typically install new updates as soon as they’re available, so I believe I was up to date before that. The first problem I noticed was that all my extensions were disabled on a remote host, and I was unable to reinstall them due to something like the extension server not being available. Some cursed nonsense from claude (manually creating a file which seemed to be missing) managed to fix the extension issue: mkdir -p ~/.cursor-server/cli/servers/Stable-f3f5cec40024283013878b50c4f9be4002e0b580/server/extensions
But then I noticed the chat window issue and haven’t been able to resolve it. Reloading the window, quitting and restarting, and “Restart Extension Host” have all failed to help. Here’s an example copy of the request details:
Request ID: 37d5e4c1-9a20-40a6-9602-5d81602f7599 {“error”:“ERROR_CUSTOM”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond within 16 seconds. 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/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11433:8255 at async wWf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11433:6308) at async EMg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:551502) at async CW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9097:16084) at async v1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11433:1205) at async Hcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34237:14278) at async ngc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34247:3575) at async ngc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34247:5180) at async ngc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34247:8576) at async OTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9172:14624) at async Xi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32996:3808)
Update: I reverted to cursor version 2.3.35, which is the most recent non-broken one I could find here ( Download · Cursor ), and no longer have this issue. So I’m pretty sure something is importantly broken about the most recent version.
I am experiencing the exact same issue with versions cursor_2.4.36_amd64.deb and cursor_2.4.37_amd64.deb on Linux Mint 22.2. However, after downgrading, version cursor_2.3.35_amd64.deb is working again.