Error while using Cursor after Claude Feble 5

Request ID: 8b8c7a6e-a865-4d64-b321-bca673cbddfd
{“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 MQp (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8723:38906)
at $fi.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8723:44299)
at async DKl._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18901:4326)
at async xOe (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7454:11718)
at async vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18901:9099
at async xOe (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7454:11718)
at async DKl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18901:8996)
at async DKl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18901:33366)
at async SHe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8705:3052)
at async SHe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8696:68121)
at async _Jp.submitMessage (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8752:39592)
at async MB0.submitMessage (vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20105:26512)
at async vscode-file://vscode-app/c:/Users/altai/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:16848:87206

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)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something 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!


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!

Hey @Altair_Beterelli_Gon, thanks for the report!

his error means the local Cursor component that runs agent requests (the extension host) stopped responding on your machine. It’s unrelated to which model you picked, so Claude Fable 5 isn’t the cause.

From what we can see, things recovered after you reloaded. If it happens again: fully quit and restart Cursor (not just Reload Window), and if it keeps recurring, let us know your Cursor version), whether you’re working locally or over Remote-SSH/WSL, and roughly how often it happens!

Hi Colin.
Tks for your answer.
I’ve already tried everything you mentioned, including fully quitting and restarting Cursor. I even uninstalled and reinstalled it, but the problem persists.

I’m working locally, not through Remote SSH or WSL. This is happening constantly, and I’m currently unable to work because of it.

Version: 3.17.21 (user setup)
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: Agent Window
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.291
OS: Windows_NT x64 10.0.26200

Thanks @Altair_Beterelli_Gon

Could you try the workaround described in this thread? The issue looks very similar.

I have already followed all of these steps, but the error persists, and I’m still unable to complete my tasks.

I have also completely uninstalled and reinstalled Cursor, but nothing has resolved the issue or made Cursor work properly again.

Great that it worked! Here’s a summary you can post:


Fixed: “Agent Execution Timed Out” error

I was getting The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. in Cursor. Uninstalling/reinstalling Cursor did NOT fix it, since those local config folders survive a reinstall.

What fixed it: fully clearing the local config/cache folders (not just reinstalling the app):

  1. Closed Cursor completely (checked Task Manager to make sure no Cursor process was still running in the background)
  2. Renamed (didn’t delete, just in case) these folders:
    • %APPDATA%\Cursor
    • %LOCALAPPDATA%\Cursor
    • %USERPROFILE%\.cursor
  3. Reopened Cursor — it rebuilt everything from scratch and I had to log in again
  4. The agent worked normally after that

Also worth noting: at the time, Cursor’s own status page had an open incident about elevated errors for some Claude models, so if you’re hitting this too, it might be a combination of a stale local extension host state + provider-side instability.

Although I marked the issue as resolved yesterday, the problem returned today, and I am once again receiving an “Agent execution timeout” message. Could someone please help me? I’m currently unable to work, and I have a project deadline to meet.

Hi @Altair_Beterelli_Gon, sorry it came back. From our side, your machine works normally most of the time, and the error appears when the component that runs agent requests briefly freezes. Clearing those folders forces a rebuild, which is why it looks fixed for a while, but it does not remove whatever is causing the freezes, so they come back.

If you can, try adding Cursor’s installation folder and %USERPROFILE%\.cursor to your antivirus or security software’s exclusions (real-time scanning is a common cause of these freezes, and it survives both a reinstall and clearing those folders), and temporarily disable any third-party extensions you have installed.

These docs are really helpful!