Bug Agent execution Timed Out. The agent execution provider did not respond in time

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Every time i ask something in the Agent, is say the Agent execution timed out. Moreover after trying to fix the bug by reinstalling cursor, now the desktopApp doesn’t recognize that i have Pro plan or that I want dark theme.

Here is the request if it can help : Request ID: 9f4f0700-24fc-4e42-8aa6-7a187f156ac3
{“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 oHv (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:25077)
at vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:30743
at async hc_.createExecInstance (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:25524)
at async fLy (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29023:658075)
at async uV.execute (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29222:10334)
at async ec_.execute (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:7435)
at async Emh.execute (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:1792)
at async XK_.execute (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41618:5015)
at async jCh.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:4745)
at async jCh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:7705)
at async jCh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:19379)
at async Qbt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29342:17002)
at async yd (vscode-file://vscode-app/c:/Users/El%C3%A8ve/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40612:4226)

Steps to Reproduce

write anything in the agent

Expected Behavior

The agent should respond me something. The desktop app should see that I have Pro plan.

Operating System

Windows 10/11

Version Information

Version: 3.3.16 (user setup)
VSCode Version: 1.105.1
Commit: 7f0f522221d0ba220e4edb766bb3c47c08c14ab0
Date: 2026-05-06T20:40:56.501Z
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.19045

Additional Information

It’s the second time I have this bug. the first time it was fixed by itself when i launched cursor 2 days after. For each new day when I launch cursor, the agent timed out BUT when I quit the folder, quit Cursor and reopen my recent project the agent was able to respond me. Moreover my Pro plan was taking in account

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey, yep this is a known bug. The extension host sometimes doesn’t register the agent execution provider before the timeout. It happens most often on Windows on 3.2.x and 3.3.x. The team is aware, no ETA for a fix yet.

Workarounds that help most users:

  • Reload Window: Ctrl+Shift+P then Developer: Reload Window or click Reload Window in the error popup.
  • Legacy Terminal: Cursor Settings > Agents > enable Legacy Terminal.
  • Start Cursor with extensions disabled to rule out a conflict: run cursor --disable-extensions in a terminal. If the error goes away, one of the extensions is causing it, often Git Blame and similar. See Initializing extensions... breaks extensions functionality and slows down Cursor IDE
  • Full restart of Cursor, close all windows, not just minimize.

You already noticed reopening the project helps. That is the same kind of extension host re-init, so the symptom matches.

About the Pro badge and theme after reinstall, that is separate and not related to the timeout.

  • If Pro didn’t show up, sign out and sign in again via Cursor Settings, top right on the account page. Usually the status updates right away.
  • Theme: after a full reinstall settings reset, so just set a dark theme again: Ctrl+K Ctrl+T then pick Dark+.

If the timeout still happens regularly after the workarounds, send:

  • your list of enabled extensions
  • a screenshot from Ctrl+Shift+P then Developer: Open Process Explorer so we can check if extensionHost is stuck.

If we get an update on the fix, I’ll post it here.