Help！！！The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 8e289571-1887-4c18-af22-c1e9d71ac159

Neo3 · August 23, 2026, 8:43am

Request ID: 8e289571-1887-4c18-af22-c1e9d71ac159
{“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 bZp (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8703:38906)
at lbi.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8703:44299)
at async qQl._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:4326)
at async cFe (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7434:11718)
at async vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:9099
at async cFe (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7434:11718)
at async qQl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:8996)
at async qQl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:33366)
at async oze._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8685:3052)
at async oze.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8676:75575)

system · August 23, 2026, 8:43am

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
Terminal & commands
Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
MCP & tools
Cloud Agents & Automations (cursor.com/agents, scheduled/event)
BugBot & Code Review
Cursor CLI
Cursor Mobile
Remote (SSH / Dev Containers / WSL)
Account, billing & login
Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

…
…
…

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

Windows 10/11
MacOS
Linux

Version Information

For Cursor IDE: Menu → About Cursor → Copy
For Cursor CLI: Run agent about in your terminal

IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Neo3 · August 23, 2026, 8:50am

Windows 10/11
yes, cursor is unusable .
Request ID: 76cf59a7-b90f-41bf-83aa-226cab2a2d22
{“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 bZp (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8703:38906)
at lbi.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8703:44299)
at async qQl._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:4326)
at async cFe (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7434:11718)
at async vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:9099
at async cFe (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7434:11718)
at async qQl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:8996)
at async qQl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:33366)
at async oze._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8685:3052)
at async oze.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/01493610/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8676:75575)

Neo3 · August 23, 2026, 9:43am

help me！！！

deanrie · August 24, 2026, 6:37am

Hey, thanks for the report. This error means the part of Cursor that runs agent commands didn’t start up in time, so the request never reached our servers. It’s not something in your settings.

To narrow it down, can you share a couple details?

Does Reload Window help Ctrl+Shift+P then type Developer: Reload Window. Does the agent work again after that?
Does it happen in every project, or only one specific folder? If it’s only one folder, open it and check if you see the prompt Do you trust the authors of the files in this folder? If you do, accept it and try the agent again.
Are you working locally, or via Remote SSH or WSL?
Please send your Cursor version Cursor > About Cursor > Copy.

Also please check Check for Updates. We’ve made improvements in this area recently, so it’s worth making sure you’re on the latest version.

Let me know how it goes.

Neo3 · August 25, 2026, 4:53am

Hi Dean,

1 . Does not help at all, I reloaded several times.
2 Yes, it happen to every project , even the new one I just started.
3 I working locally
4 Version: 3.17.19 (user setup)
VS Code Extension API: 1.128.0
Commit: ae3a2b7231dd56194447fe4570dfdc61640b1e90
Layout: Agent Window
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.19045

Dean Rie <[email protected]> 于2026年8月24日周一 14:47写道：

deanrie · August 25, 2026, 6:29am

Thanks for the details, they helped narrow down the cause.

It looks like the component that runs agent commands cursor-agent-exec can’t start because PowerShell isn’t available on the machine. It’s probably blocked or removed from PATH by corporate policy. Based on the install path, this looks like a managed machine. Because of that, every agent request times out before it even reaches our servers. That explains why Reload Window doesn’t help and why it breaks in all projects. It’s not something in your project settings.

This is a known issue we’re tracking. Updating the version by itself doesn’t fix it yet, but there’s a working workaround: switch the default terminal to Git Bash.

Make sure Git for Windows is installed.
Open the Command Palette Ctrl+Shift+P then 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"

If Git is installed in a different folder, update the path.

In Cursor Settings > Chat, check that Legacy Terminal Tool is turned off. That’s the default.
Fully close and reopen Cursor. Do a real restart, not Reload Window.

This same workaround is confirmed to work for another user with the exact same issue. Let me know if it helped.

Neo3 · August 25, 2026, 9:36am

It seems working again, thanks bro

Dean Rie <[email protected]> 于2026年8月25日周二 14:39写道：

Topic		Replies	Views
Agent Execution Timed Out – Extension Host not responding Bug Reports chat	2	51	August 24, 2026
ERROR_EXTENSION_HOST_TIMEOUT on two Windows PCs — reboot often required Bug Reports chat , crashes , windows	1	41	August 27, 2026
The agent execution provider did not respond within 4 seconds. This may indicate the extension host is not running or is unresponsive Bug Reports extensions , performance	13	8966	January 31, 2026
Cursor window frozen Bug Reports performance , crashes	15	447	April 23, 2026
"Agent execution timed out" - can't use cursor on windows-11! Bug Reports extensions , crashes , windows	2	205	April 12, 2026

Help！！！The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 8e289571-1887-4c18-af22-c1e9d71ac159

Related topics