Ubuntu - Agent Execution Time Out

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m unable ro run any prompt. whatever i do i just endup at this error.

Steps to Reproduce

I open IDE run any prompt after like 10 sec it says Agent Execution Time Out.

Expected Behavior

It should not time out

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
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: Linux x64 5.19.0-46-generic

For AI issues: which model did you use?

I use Auto.

For AI issues: add Request ID with privacy disabled

Request ID: 2c788a53-3031-4d99-b39e-c534e7533135
{“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 Tyy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:26479)
at vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:30622
at async JRS.createExecInstance (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:26926)
at async wXw (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29229:646049)
at async rz.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29428:10334)
at async axt.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:9201)
at async OGh.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38816:1792)
at async Av0.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41806:4995)
at async Vnm.buildComposerRequestContext (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:4741)
at async Vnm.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:7696)
at async Vnm.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:19567)
at async lCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Va (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4230)

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is a known class of bugs with the extension host on our side ERROR_EXTENSION_HOST_TIMEOUT. The request doesn’t even reach the backend, so you get the error after about 30 seconds on any prompt. No ETA for a fix yet.

A few steps that often help:

  1. Reload Window: Ctrl+Shift+P then Developer: Reload Window. If that doesn’t help, fully restart Cursor.
  2. Disable extensions: run cursor --disable-extensions in your terminal and see if it still happens. If it stops, some extension is crashing the host.
  3. Developer Tools: Help → Toggle Developer Tools then open the Console tab. Send the errors from there if you see any.
  4. On Ubuntu with kernel 5.19, clearing the cache sometimes helps. Close Cursor and delete ~/.config/Cursor/Cache, ~/.config/Cursor/CachedData, ~/.config/Cursor/Code Cache.

If nothing helps, run Ctrl+Shift+P then Developer: Export Logs and attach the zip, I’ll take a closer look. Your kernel version is pretty old 5.19.0-46, so if you can update to a newer one, it’s also worth trying.

@deanrie Thanks for the reply. I’ve exausted all the suggestions you made but none of them worked.

Tho i was able to fix issue appearntly these extentions are the culprits.

sudo rm -f /usr/share/cursor/resources/app/extensions/cursor-agent-exec/dist/621.js
sudo rm -f /usr/share/cursor/resources/app/extensions/cursor-mcp/dist/138.js

I hope it helps team to figure out issue.

Wasi.