Cursor is not working, Agent execution timed out

Support Bug Reports
1

It keeps planning the next move, takes longer than expected, and eventually times out. Please fix ASAP

Request ID: 29c69e2f-fc98-482c-8d0c-e55d44b7f74b
{“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 FY_ (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45283:26650)
at j8f.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45283:29709)
at async OKf._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48288:4333)
at async OKf.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48288:7630)
at async OKf.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48288:19576)
at async Vyn.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35985:17397)
at async zh (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47271:3889)

image
image398×156 5.42 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

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.