Agent Execution Timed Out – Extension Host not responding

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: f40bf9f3-0887-40e5-b0f7-f6a022ebb426
{“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 $zu (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7325:38655)
at gMi.waitForProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7325:44093)
at async Gpo._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:4328)
at async yye (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7022:12023)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:9084
at async yye (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7022:12023)
at async Gpo.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:8981)
at async Gpo.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:32107)
at async BTe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7296:2568)
at async BTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7287:72977)

Steps to Reproduce

Open Cursor.
Open Agent.
Send a message or try to connect.
The timeout error appears.

Screenshots / Screen Recordings

output.log (39.6 KB)

25.png
25.png1686×970 37 KB

Operating System

Windows 10/11

Version Information

Version: 3.15.6 (system setup)
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: add Request ID with privacy disabled

Request ID: f40bf9f3-0887-40e5-b0f7-f6a022ebb426
{“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 $zu (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7325:38655)
at gMi.waitForProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7325:44093)
at async Gpo._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:4328)
at async yye (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7022:12023)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:9084
at async yye (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7022:12023)
at async Gpo.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:8981)
at async Gpo.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15007:32107)
at async BTe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7296:2568)
at async BTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7287:72977)

Additional Information

attaching the Log file

Does this stop you from using Cursor

Yes - Cursor is unusable

10

Hey @kaha, thanks for the detailed report and the log!

The component that runs Agent commands can’t start because PowerShell isn’t accessible on your machine (it’s blocked and removed from PATH by policy), so every Agent message times out before it ever reaches our servers. Your team is already in touch with us about this exact issue, and I’ve added your report to it.

To get working again:

  1. Update Cursor to the latest version (3.17).
  2. Make sure Git for Windows is installed, then set Git Bash as your default terminal with an explicit path. Open the Command Palette (Ctrl+Shift+P) → “Preferences: Open User Settings (JSON)” and add:
"terminal.integrated.profiles.windows": {
  "Git Bash": { "path": "C:\\Program Files\\Git\\bin\\bash.exe" }
},
"terminal.integrated.defaultProfile.windows": "Git Bash"
  1. In Cursor Settings → Chat, make sure Legacy Terminal Tool is turned off (it’s off by default).
  2. Fully quit and reopen Cursor (not just Reload Window).

This exact setup was verified working on another machine at your company that hit the same issue. Let us know how it goes!

11

@Colin
Thank you very much for your quick response. Your suggestions helped me a lot. I updated the User Settings JSON to use Git Bash, and the Agent is working now. I will also update Cursor to version 3.17. If I run into any issues after the update, I will let you know.