App continuously crashes: Agent Execution Timed Out

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent Execution Timed Out

The agent execution provided did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: c57eaf3b-6554-461a-a113-03f996a59535

This is the error msg. After 5-6 prompts it happened. Not even heavy prompt cause it didn’t actually build anything. It just did some research and told how the tech stack of a task tracker should look like and how it is planning to do it.

Please help me solve it its an expensive license. Very Unsatisfactory

Steps to Reproduce

It is reproducing on its own tbh and at random moments. I can still give you the prompts I entered in the chat

  1. Help me with my project. I want to build a task tracker.
  2. I said - Just go with whatever you think is best. But you want into explaining? just trying to understand why
  3. To its questions I answered - “Just go with whatever you think is best” & “Before you start, show me your plan — high level first, then steps”
  4. It showed me a plan and thinking.
  5. Use the spec from the file I attached. - It replied that it cannot see any file attached.
  6. Forget the file. Just set it up — go.

After this it broke

Expected Behavior

it was supposed to start building based on its own plan. But it started crashing, agent timeout.

Tried reloading, closing & restarting, relogging in but it doesn’t go away anyway. Removing the state file works but i don’t want to loose my valuable chats

Screenshots / Screen Recordings

Cursor Issue.png
Cursor Issue.png512×146 14.5 KB

Operating System

MacOS

Version Information

Version: 3.2.16 (Universal)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z (10 hrs ago)
Layout: glass
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: Darwin arm64 24.6.0

For AI issues: which model did you use?

Auto, Opus 4.6, Opus 4.7 - all same issue

For AI issues: add Request ID with privacy disabled

Request ID: c57eaf3b-6554-461a-a113-03f996a59535

Request ID: 3b6d2e00-1064-40cc-b487-de5f94e2e6c5
{“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/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38816:21732)
at oVh.waitForProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38816:24753)
at async mim._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:4045)
at async mim.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:7626)
at async mim.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async hCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async ORC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45410:99408)
at async I7C.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46428:17064)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43480:28443

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi @Swarnendu_Bhattachar

This is a known issue — the extension host is timing out before it can register the agent execution provider, and our team is actively working on a fix.

Since you mentioned that removing the state file works, but you don’t want to lose your chats, here are some things to try that don’t involve deleting state:

  1. Restart Extension Host — press Cmd+Shift+P, type Developer: Restart Extension Host, and run it. This restarts the extension host process without clearing any data.

  2. Start a new chat — if the issue is tied to a specific conversation’s state, opening a fresh Agent window may work while preserving your existing chats.

  3. Check your state.vscdb file size — this file can grow very large and cause the extension host to become unresponsive. You can check it at ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb. If it’s over 1-2 GB, that’s likely contributing to the problem.

  4. Test in an empty folder — try mkdir ~/test-project && cursor ~/test-project and submit a simple prompt. If it works there, the issue may be workspace-specific, which would help narrow things down.

If none of these help, could you share:

  • The output from Help > Toggle Developer Tools > Console at the moment the timeout happens (look for any red errors mentioning extensionHost or cursor-socket)

This will help us identify whether something specific to your environment is causing the extension host to get stuck.

8

Let me try #1. will revert back.

#2,3,4 are not helpful. Tried reloading, opening new chat and testing in an empty/ new folder, same error since last night. Also, size of the state file is below 2 MB. When I tried renaming it then also it was below 2 MB and even now.

9

image
image1084×1078 192 KB

image
image1084×1078 175 KB

10

Thanks for the console output. Two things stand out:

  1. The apidev.azure-api-center extension is requesting API features that no longer exist in this version of Cursor. That can destabilize the extension host. Could you try disabling it (Cmd+Shift+X, search for “Azure API Center”, click Disable) and see if the timeout stops?

  2. Plugin loading is also running slow (~3-4 seconds per call). If disabling the Azure extension alone doesn’t help, try disabling all non-essential extensions temporarily to test whether one of them is the root cause. You can do this quickly with Cmd+Shift+P > Extensions: Disable All Installed Extensions.

Also, did the Restart Extension Host command (Cmd+Shift+P > Developer: Restart Extension Host) make any difference when you tried it?

If disabling extensions doesn’t resolve things, try to capture the console output right at the moment the “Agent Execution Timed Out” error appears (scroll to the bottom of the Console tab right when it happens) — the screenshots you shared show the startup logs, but the timeout error itself would appear later.

11

Same here. Source control window also doesn’t show up (no source control providers…) Extensions are not visible. Agents don’t work. Developer: Restart Extension Host didn’t do anything.

Basically the whole program is rendered useless. It would be great if just a litttttle more QA testing is done before releasing new version.

12

Both the suggestion didn’t work.

  1. apidev.azure-api-center is not even installed.
  2. Disabled All Installed Extensions.

Developer: Restart Extension Host didn’t do any help either.

13

Sorry, you’re hitting this too.

This is a known issue our team is working on. Since your symptoms are a bit different from this thread (source control and extensions also not visible), could you create a new thread with your version info (Help > About) and a request ID from a failing attempt? That way our team can track your specific case properly.

14

Since the extension isn’t installed and disabling everything didn’t help, this rules out third-party extensions as a factor, which is actually useful data. At this point, the issue is on our side. I don’t have a specific ETA, but this is high priority given the number of users affected.

In the meantime, one last thing worth trying: fully quit Cursor (not just close the window — Cmd+Q), then reopen. If even that doesn’t work, try launching from the terminal with extensions disabled:

cursor --disable-extensions

If agents work with --disable-extensions but not otherwise, that narrows things further. If they still don’t work even with that flag, then it confirms the issue is in the core extension host startup itself, which aligns with what our team is investigating.

I’ll follow up here once the fix ships.