Timing out bug all the time

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Request ID: 86db902b-c4d6-4e79-89c2-3efcbdda9ff7
{“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 ULw (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44341:28583)
at VKd.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44341:33347)
at async _bf._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47691:4084)
at async _bf.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47691:7354)
at async _bf.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47691:19276)
at async Zut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36407:17835)
at async lRE.submitMessage (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:57492:278557)
at async nWE.submitMessage (vscode-file://vscode-app/c:/Users/Anna%20Edmonds/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:58528:20504)

Steps to Reproduce

every time i say something as short as hi it times out

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

6

This is a known issue our team is actively working on. The timeout happens because the extension host isn’t starting up properly on your machine.

A couple of things to try that have been working for other users on your team:

  1. Trust the workspace via the classic editor: Open a terminal and run cursor --classic . from the folder where the timeout is happening. This opens the classic editor view and should show a “Trust this workspace” prompt. Click “Yes, I trust the authors,” then close the classic window and try the agent again. You may need to do this once per project folder.

  2. Add Cursor to your antivirus/EDR exclusions. If your machine has endpoint protection software, ask your IT team to exclude these paths from real-time scanning:

    • C:\Users\<your username>\AppData\Local\Programs\cursor\

    • C:\Users\<your username>\.cursor\

    • Your project folders

  3. Make sure you’re on the latest version: Open Cursor and go to Help > Check for Updates.

For more details on endpoint security configuration, see our Endpoint Security guide.

If the issue persists after trying these steps, could you export your logs? Open the Command Palette (Ctrl+Shift+P), type “Developer: Open Logs Folder,” and share the log files from the newest session (especially any files with “exthost” or “extension-host” in the name). That will help us narrow down the exact cause on your machine.