Cursor unusable for days now - Agent Execution Timed Out

[lmedia (LM)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor has been totally unusable for days. Two things are broken, both appear to point at the same underlying problem (the agent/extension host not responding):
▎
▎ 1. Models in the IDE fail with: “The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.” (see screenshot
▎ — the timeout has a “Reload Window” button).
▎ 2. Commit message auto-generation gets stuck indefinitely on “Generating…” and never completes.

Steps to Reproduce

1. Open Cursor on macOS (v3.6.31).
   ▎ 2. Try to use any model in the IDE → “Agent Execution Timed Out / provider did not respond in time”.
   ▎ 3. Separately, click the auto-generate commit message button (sparkle icon) in Source Control → it shows “Generating…” forever and never produces a message.
   ▎ 4. Reloading the window does not resolve it; the issue persists across days/restarts.

Expected Behavior

Models should respond, and commit message generation should complete, as they did before.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.6.31 (Universal)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
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.220
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Gpt-5.5 and Composer 2.5

For AI issues: add Request ID with privacy disabled

Request ID: 59995821-ecef-4818-8c2d-5a10da19350a
{“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 ULw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44341:28583)
at VKd.waitForProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44341:33347)
at async _bf._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47691:4084)
at async _bf.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47691:7354)
at async _bf.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47691:19276)
at async Zut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:36407:17835)
at async Object.$s [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46696:3887)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45757:103088

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, this is a known issue. It’s the ERROR_EXTENSION_HOST_TIMEOUT error Agent Execution Timed Out when the extension host stops responding. Your stack trace and version match what we’re already tracking, so it’s a bug on our side, not your setup. I can’t share an ETA yet, but the issue is being worked on, and I’ll post an update in the thread once I have one.

A few things that sometimes help as a temporary unblock if Reload Window doesn’t work:

1. Fully quit Cursor with Cmd+Q, not just reload, then start it again.
2. Launch from the terminal with extensions disabled using cursor --disable-extensions. This can help confirm if something is making the extension host heavier.
3. If you’re behind a corporate proxy or VPN, try enabling Disable HTTP/2. App Settings, Cmd+Shift+,, then search for HTTP/2.

If none of this unblocks you, that can be expected for the persistent variant of this bug, so you’ll need to wait for an update. Let me know if any of these steps helped.