Agent execution timeout

Support Bug Reports
1

The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.Request ID: 824535d3-5679-46ce-b492-4070298e40ef
{“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 Zyy (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:21732)
at oVh.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:24753)
at async mim._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:4045)
at async mim.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:7626)
at async mim.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async hCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async ORC.submitMessage (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45410:99408)
at async I7C.submitMessage (vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46428:17064)
at async vscode-file://vscode-app/c:/Users/RAM/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43480:28443

5

Hey, this is a known bug. ERROR_EXTENSION_HOST_TIMEOUT is fixed in 3.1.17, especially on Windows. I can’t share an ETA for the fix yet, but there are a couple of working workarounds.

  1. Enable Legacy Terminal
    Settings → Cursor Settings → Agents → Legacy Terminal → enable. Restart Cursor and try again.

  2. If that didn’t help, do a clean reinstall
    In a similar thread CURSOR UNUSABLE - " Agent execution provider did not respond in time. The extension host is not running or is unresponsive. ", the root cause was a corrupted cursor-agent-exec extension file inside the installer. The hash check failed, the extension didn’t activate, and that caused the timeout. On Windows:

  • Close Cursor, open Task Manager, and kill all Cursor.exe / cursor.exe processes
  • Apps & Features → Cursor → Uninstall
  • Download the latest installer from Cursor · Download and reinstall
  • You don’t need to delete your user data at %APPDATA%\Cursor, your settings and account will stay

Please confirm your Cursor version in Help → About, and let me know if the steps above helped. If the error still happens after reinstall, we’ll need the exthost.log file from %APPDATA%\Cursor\logs\<latest session>\exthost\ and a new Request ID.