Agent Execution Timed Out - All Agents Blocked

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am still fully blocked by this service outage.

Where does the bug appear (feature/product)?**

Cursor IDE (Agent / Job Planning)

Describe the Bug

Unable to run any agent or plan any job since yesterday around 19:00 CET. The Agent consistently fails to execute requests, despite Cursor previously working without issue. The problem persists across application restarts, system reboots, and model switching.

Steps to Reproduce

Open Cursor on Windows 10.
Open any project workspace.
Open the Agent / Planning panel.
Attempt to run an agent prompt or plan a job using any model (or Auto mode).
The request fails to execute or process.
Expected Behavior

The Agent should accept the prompt, generate a plan, and execute tasks as expected.

Operating System

Windows 10

Version Information

IDE: Cursor

OS: Windows 10

For AI issues: which model did you use?

Tested with multiple models, including Auto mode.

For AI issues: add Request ID with privacy disabled

Request ID: 3178226c-5cf9-41de-a99b-e641d874f8de
{“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 vum (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:39609)
at vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:47940
at async kum.createExecInstance (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:41811)
at async Rzh (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7428:74375)
at async KC.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7596:4747)
at async Xcm.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:15398)
at async vHr.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:6147)
at async wX0.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20812:1734)

Additional Information

Issue began around 19:00 CET yesterday.
Troubleshooting attempted: restarted Cursor, switched models, enabled Auto model mode, and rebooted the PC twice.
No changes were made prior to the issue; Cursor functioned normally until this point.
Does this stop you from using Cursor

Yes - Cursor is unusable for agent and job planning tasks.

Steps to Reproduce

Open Cursor, enter anything in the agent and wait for time out.

Expected Behavior

I expect to be able to use the agents för planning or implimentation/coding.

Screenshots / Screen Recordings

Capture.PNG
Capture.PNG1109×209 13.6 KB

Operating System

Windows 10/11

Version Information

Version: 3.21.9 (user setup)
VS Code Extension API: 1.128.0
Commit: 9998796a6096ce83d83a9332bfe7473b985db750
Date: 2026-09-17T02:16:48.732Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

All. tried All including Auto.

For AI issues: add Request ID with privacy disabled

Request ID: b7b77cff-2ccf-48d2-ba78-ab1f358a5e89
{“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 vum (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:39609)
at vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:47940
at async kum.createExecInstance (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:41811)
at async Rzh (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7428:74375)
at async KC.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7596:4747)
at async Xcm.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:15398)
at async vHr.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8866:6147)
at async wX0.execute (vscode-file://vscode-app/c:/Users/calle/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20812:1734)

Additional Information

I axpect to be compensated for this complete service outage.

Does this stop you from using Cursor

Yes - Cursor is unusable

10

I tried all these four steps with no change:

"Hey, thanks for the report. This is a known bug. ERROR_EXTENSION_HOST_TIMEOUT shows up when the extension host doesn’t start up and register the agent execution provider in time. It happens most often on Windows. We’re already tracking the issue, but I can’t share an exact ETA for a fix yet.

For now, try these workarounds in order:

  1. Click “Reload Window” in the popup, or run Ctrl+Shift+P then “Reload Window”. If that doesn’t help, fully restart Cursor.
  2. Temporarily start without extensions: run cursor --disable-extensions from the command line. If the error goes away, it’s likely a heavy extension. Disable extensions one by one to find the culprit.
  3. Enable “Disable HTTP/2” in settings: App Settings Ctrl+Shift+, then search for “HTTP/2” and enable it. This often helps on corporate networks, VPNs, or with antivirus software.
  4. Check if your antivirus is scanning the Cursor folder c:\Users\Admin\AppData\Local\Programs\cursor\. You can add it to exclusions so the extension host starts faster.

Let me know if any step helped. If it’s still happening, share your Cursor version Menu > About Cursor > Copy, and whether you have any heavy extensions installed."

11

Hi @Carl_Hellstrom

The backend logs show your machine having trouble getting in touch with agentn.api5.cursor.sh.

Can you run the Network Diagnostics under Cursor Settings > Network and see if they come back clean?

12

image
image1035×223 11.8 KB

13

All is green when running Network Diagnostics

17

I am having the same issue as well. I have tried everything you have tried as well. I reinstalled the app, and I am up to date on the versioning as well. It worked momentarily on the side tab for the ide but Agent’s window hasn’t worked in two days. Cursor support is saying it’ll take 12-48 hours to get an update on this. This is a huge blocker

24

What now? What is happening?

25

Hey @Carl_Hellstrom

Thanks for sticking with us. I think we found what is different about your setup, and there is a setting you can check that should get the agent working again.

  1. Open Cursor Settings.
  2. In the list on the left, click Code Intelligence. (In the classic editor window this tab is called Indexing.)
  3. Find the switch labelled “Index Repositories for Instant Grep”.
  4. If it is off, turn it on. Cursor will ask to reload the window. Click Reload Window.
  5. Open a new agent chat and send the single word hello.

Please reply with two things: whether that switch was off before you changed it, and whether the hello message now gets a response.

30

The switch was off and after I clicked it on I got:

"Hello.

I’m the execution agent for XXXXX — I can implement specs, run builds and tests, explore the codebase, and follow the triad workflow (plan → Claude validation → execute).

What would you like to work on today?"

31

The issue is fully resolved now! What was the root cause? I did not change that setting and it worked until it didn’t?

32

Having a similar issue but index repositories was already checked. Request ID for the chat that’s hanging right now: b85b9683-7050-4c9b-8a08-84e399b4e837

33

Looks like my issue was related to a recent OS upgrade. Found my solution here: Cursor Agent gets stuck while exploring files and never generates a code change on macOS 27 - #11 by Charlie_K

36

Hey @Carl_Hellstrom,

Glad turning that switch back on got you going again, and thanks for confirming it had been off.

To answer your question: a recent change in how Cursor runs agents didn’t handle the case where “Index Repositories for Instant Grep” is turned off, so every request waited and then timed out. That switch can also end up off from an older setting carried over from previous versions, which may be why it looked like nothing changed on your side.

A fix is coming in Cursor 3.21.18, so the agent will work whether that switch is on or off. Until you’ve updated, just keep the switch on.

cc @usman.khan