When I start a new chat thread, it does not respond until timed out. No any luck by reloading window and resubmit.
It reported:
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 696d4fc6-b9e1-474f-b250-0245f4def2c5.
Reload window does not resolve the issue.
Steps to Reproduce
Just start a new agent chat and submit, no any respond until timed out. Retry didn’t resolve the issue.
For AI issues: add Request ID with privacy disabled
Request ID: 696d4fc6-b9e1-474f-b250-0245f4def2c5
{“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”:}}
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at zlb (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38281:25776)
at vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38281:29901
at async FcS.createExecInstance (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38281:26223)
at async wO_ (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28682:630571)
at async OF.execute (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28903:7917)
at async sfd.execute (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38281:1792)
at async pGS.execute (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41276:4969)
at async zkd.buildComposerRequestContext (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41286:4739)
at async zkd.streamFromAgentBackend (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41286:7610)
at async zkd.getAgentStreamResponse (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41286:18486)
at async B3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Users/I511982/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29014:16809)
Hey @Kane_Gong, would you mind going in the settings and running a network diagnostics? it will help the team to figure out the issue! see below how to do it
oh well, since that’s the case, in the failing project, you could try running the Start Extension Bisect! to do that, open said project, then do CMD + SHIFT + P and enter Start Extension Bisect, run it and try out each and individual Extension to see if disabling some fixes your issue!
After switching to classic mode using the command “cursor --classic”, the previous failed workspace was blocked by the trust folder (see screenshot). After marking the folder as trusted and switching back to non-classic mode, the issue disappeared.
oh nice! I’ll let you mark the issue as now fixed then, we will learn from this and maybe some more context into the error message so that things are clearer! thanks for following through rapidly, hope you have great days ahead using cursor!
