"Agent execution timed out" - can't use cursor on windows-11!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: e7d0ddb3-988d-439a-bc81-1898f0670498 (details below)
I’m on latest version (details below).

As a last ditch effort, I re-installed & the issue still exists.

Tried starting with “cursor --disable-extensions” but the issue persists.

Any ideas ?

Steps to Reproduce

When I start cursor IDE - it shows me an error - “Extension host terminated unexpectedly”.
And all composer requests fail after “Planning next moves”.

Expected Behavior

It should plan & execute code changes

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
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
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

composer 2 or Auto - fails for all

For AI issues: add Request ID with privacy disabled

Request ID: 05f7b4a6-ac5f-4af3-aca4-a3e06e685739{“error”:“ERROR_CUSTOM”,“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 Outat vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:53345:23460at async fg_.createExecInstance (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:53345:20015)at async mqy (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43738:623141)at async $4.execute (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43959:14688)at async Khd.execute (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:53345:1749)at async wK_.execute (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56367:4966)at async k0d.buildComposerRequestContext (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:4190)at async k0d.streamFromAgentBackend (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:6906)at async k0d.getAgentStreamResponse (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:17325)at async XOe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44075:19892)

Additional Information

Re-installing + Restarting didn’t help.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is a known issue. The extension host cursor-socket can’t start, and all AI requests time out. The team is aware, and the bug is logged.

A few things to try:

  1. Check the cursor-socket folder contents. Open PowerShell and run:
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"

You should see an out\ folder or dist\. If there is no out\ but there is dist\, create a symlink:

cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
New-Item -ItemType SymbolicLink -Name "out" -Target "dist"

You need to run PowerShell as admin.

  1. Try opening a new Agent window instead of the current one. One user with the same error got unstuck that way.

  2. Turn off Codebase Indexing: Cursor Settings > Indexing & Docs > turn off Codebase Indexing. Then reload the window using Ctrl+Shift+P and run Developer: Reload Window.

  3. If none of the above helps, open Developer Tools via Help > Toggle Developer Tools, go to the Console tab, wait for the error to show up, and paste all the red entries here.

Let me know how it goes.

1 Like

I think I had copied it directly instead of creating the symlink.. which didn’t work.

I also, disabled the index repositories for Instant Grep Beta.

One of those worked !

1 Like