Cursor Agent Time out issue ( Multiple Agent case )

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent Execution Times out if I open multiple agent at a time, I dont have any plugin running. even after reloading window multiple time it is not working. only way is to close other agents and have this agent only running. Looks like some thing getting bloating if we have multiple agent running.

Steps to Reproduce

Open multiple agent and with different repo’s.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (system 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

For AI issues: which model did you use?

Any model

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Mahesh_S!

This is a couple of versions behind. Can you check if you’re still experiencing the issue on the latest version (3.10)?

Updated to latest version – Same issue

Request ID: 5192c1d8-2d4f-4e8a-9268-d93e390e52a9
{“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 Dgp (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9123:32291)
at AQi.waitForProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9123:37347)
at async lba._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:3913)
at async fAe (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7918:12023)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:8049
at async fAe (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7918:12023)
at async lba.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:7973)
at async lba.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:23432)
at async VIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9229:2399)
at async Object.wk [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:19518:83910)

-- Version: 3.10.20 (system setup)
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0

xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Thanks, @Mahesh_S!

I took a look at the recent request ID, and it appears you’re running into very low memory (RAM) availability when the extension host fails to start. It’s expected that running multiple agents simultaneously will create some memory pressure.

How many GB of RAM does your local workstation have? And how much RAM is free before you start Cursor?

I have 16GB memory. At this time happens when I have single cursor session, Memory is 92% while cursor is running.

And before Cursor is running?

Before it was 70+ %

We’re always working to make Cursor more memory efficient, but in the short term, it sounds like there’s not a lot of headroom for Cursor to run well, and the more agents you have running at a time, the more memory pressure will be put on your system.

I’d suggest freeing up some RAM before starting Cursor, or seeing if it’s possible to have a system with more memory.