Agent execution timed out during agent planning

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Version: 3.6.21 (user setup)
VS Code Extension API: 1.105.1
Commit: e7a7e93f4d75f8272503ecf33cedbaae10114a10
Date: 2026-05-28T21:45:36.072Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

Request ID: 837eebee-b278-4152-9c1c-634a822c6a7b
{“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 uLw (vscode-file://vscode-app/c:/Users/Vadim%20Place/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44320:28201)
at mKd.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/Vadim%20Place/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/Vadim%20Place/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/Vadim%20Place/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/Vadim%20Place/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/Vadim%20Place/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36386:16963)
at async KEE.submitMessage (vscode-file://vscode-app/c:/Users/Vadim%20Place/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57464:274081)
at async t7E.submitMessage (vscode-file://vscode-app/c:/Users/Vadim%20Place/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58492:20504)

Steps to Reproduce

During agent creation, agent execution time out error systematic

Operating System

Windows 10/11

Version Information

Version: 3.6.21 (user setup)
VS Code Extension API: 1.105.1
Commit: e7a7e93f4d75f8272503ecf33cedbaae10114a10
Date: 2026-05-28T21:45:36.072Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

6

This is a known issue affecting the Agents Window (Glass) when a project folder hasn’t been “trusted” yet. Glass doesn’t currently show the workspace trust prompt that the Editor window does, so the agent silently times out instead.

Here’s what should fix it:

  1. Open a regular terminal and navigate to your affected project folder

  2. Run: cursor --classic .

  3. This opens the Editor and shows the “Do you trust the authors of the files in this folder?” dialog. Click Yes, I trust the authors

  4. Close the Editor window, then try using the agent in that folder again from the Agents Window

You’ll need to do this once per project folder that’s giving you the timeout. After a folder is trusted, the agent should work normally going forward.

Also, check if you have "security.workspace.trust.emptyWindow": false in your settings. If so, removing that line (or setting it to true) can also resolve this.

Our team is actively working on a fix to surface the trust prompt directly in the Agents Window so this workaround won’t be needed.