Cursor Agents stuck

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor 3 Agent Window is just broken in windows again. The agent chat is stuck at ‘Taking longer than expected…’ or throwing error

Request ID: 0f743527-9c39-4e37-ad40-441fbc267f84
{"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 $Vv (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38788:25077)
    at sfh.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38788:29583)
    at async h1h._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41789:4218)
    at async h1h.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41789:7804)
    at async h1h.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41789:19638)
    at async ryt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29503:16976)

Steps to Reproduce

Just run the Agent Window in windows or wsl2 project.

Expected Behavior

It to works fine

Screenshots / Screen Recordings

Screenshot 2026-05-11 221049.png
Screenshot 2026-05-11 221049.png400×124 1.81 KB

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (user setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
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
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Any model

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this is a known issue with extension host timeout on Windows, especially on Windows plus WSL in the latest versions. The team is aware and investigating, but I can’t share an ETA for a fix yet.

A few things that might help as a workaround:

  • Run Reload Window when it gets stuck: Ctrl+Shift+P then Developer: Reload Window. In some cases the extension host restarts and the timeout goes away.
  • If you have heavy extensions, try starting without them: cursor --disable-extensions. This helps confirm whether the extension host is overloaded.
  • In Process Explorer: Ctrl+Shift+P then Developer: Open Process Explorer, check the extensionHost process. If it’s consistently using a lot of CPU or memory, let us know.

If we get an update on the fix, we’ll reply in the thread.

7

But this was working fine around the start of May. I confirmed the timeline from the usage data in the Cursor dashboard. So what changed now?

Do we have any older version where the Agent window still works properly with WSL2?

It’s frustrating that such a core part of my development workflow can work perfectly one day and then suddenly stop working without any obvious change on my side.

8

The regression aligns with version 3.1.17+. We don’t recommend pinning to an older version as other improvements depend on the newer builds.

The team is actively working on a fix for this (the root cause has been identified). In the meantime, the workarounds @deanrie shared above (especially Reload Window when it happens) are the best path. We’ll update this thread when the fix ships.