# Agent Execution Timed Out Occur **URL:** \ **Category:** Bug Reports\ **Tags:** crashes\ **Created:** [June 8, 2026, 7:21pm UTC](https://forum.cursor.com/t/agent-execution-timed-out-occur/162730 "2026-06-08T19:21:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Atharva\_Pradhan](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Atharva\_Pradhan](https://forum.cursor.com/u/Atharva_Pradhan)\ **Post date:** [June 8, 2026, 7:21pm UTC](https://forum.cursor.com/t/agent-execution-timed-out-occur/162730/1 "2026-06-08T19:21:59Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Request ID: c8235e2e-ace8-474c-946f-b24e9ad3d070 {“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 EYw (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36419:30429) at vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36419:37871 at async DYw.createExecInstance (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36419:32408) at async qn1 (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35519:687951) at async Z3\_ (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35543:63939) at async PO.execute (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35719:14286) at async fYw.execute (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36419:10112) at async Lmh.execute (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36419:2720) at async N4x.execute (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48185:5786) at async k7g.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/Atharva/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48195:4824) ### Steps to Reproduce Open Folder → Enter Prompt → Error ### Screenshots / Screen Recordings ![Screenshot 2026-06-09 004926.png](https://us1.discourse-cdn.com/cursor1/original/3X/9/f/9fc85d457285b5b0360a19083f07490888580553.png) ### Operating System Windows 10/11 ### Version Information Version: 3.7.21 (user setup) VS Code Extension API: 1.105.1 Commit: 517f696d8ab6c53eb04fbfdaae705cd146bf3460 Date: 2026-06-07T21:46:09.237Z Layout: editor 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.256 OS: Windows\_NT x64 10.0.19045 ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [June 8, 2026, 7:32pm UTC](https://forum.cursor.com/t/agent-execution-timed-out-occur/162730/5 "2026-06-08T19:32:53Z")
Hey, this is a known issue on Windows. The extension host doesn’t start up in time, and the agent crashes with `ERROR_EXTENSION_HOST_TIMEOUT` before the request even reaches the server. We don’t have an exact ETA for a fix yet, but these steps help in most cases. Try them in order: 1. First, click Reload Window in the error popup, or fully close Cursor, then check Task Manager to make sure there are no `Cursor.exe` processes left, and start it again. 2. Check if an extension is blocking the extension host. Run this from the command line: 3. If you have antivirus or endpoint protection, add the Cursor folder to exclusions. On Windows this is a common cause, antivirus can slow down or remove extension host files: 4. Clear the cache. Fully close Cursor, delete these folders, then start it again: If none of that helps, open PowerShell as admin and send the output of this command so we can check the extension host state: ```powershell dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket" ``` Also send logs from `%APPDATA%\Cursor\logs\` from the latest session, the `main.log` file and anything with `exthost` in the filename. That should show exactly where startup is failing. Let me know which step worked, or if you’re still hitting the error. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 1, 2026, 12:08pm UTC](https://forum.cursor.com/t/agent-execution-timed-out-occur/162730/8 "2026-07-01T12:08:22Z")
Hey @Atharva_Pradhan are you still getting the “Agent Execution Timed Out” error? There have been a lot of updates since your post. You were on 3.7.21, and the current stable is 3.9.16. Please update to the latest version and try again. If it still happens after updating, follow the steps above again, especially `cursor --disable-extensions` and adding the Cursor folder to your antivirus exclusions. Then send the logs from `%APPDATA%\Cursor\logs\` from your latest session, `main.log` and any files with `exthost` in the name. That should show where the extension host startup is failing. If a recent update fixed it, no need to reply. Otherwise, let me know how it goes.