Agent Execution Timed Out – Extension host becomes unresponsive frequently (Windows)

[Mobile_Dev]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am experiencing two major issues:

Frequent “Agent Execution Timed Out” errors

“The agent execution provider did not respond within 30 seconds. This may indicate the extension host is not running or is unresponsive.”

Extremely slow agent responses

Even when it does not timeout, responses are very delayed.

Sometimes takes 30–60+ seconds before any reply starts.

Makes the editor nearly unusable.

This happens daily and significantly affects productivity.

Steps to Reproduce

1. Open Cursor.
2. Open an existing project.
3. Use the chat/agent (e.g., ask a question or run a generation).
4. Wait ~30 seconds.
5. Error appears: Agent Execution Timed Out.
6. Observe:
   → Long delay before response
   → OR timeout error after 30 seconds

Expected Behavior

The agent should respond normally within a few seconds and not cause the extension host to freeze.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

auto

Additional Information

System has 32GB RAM and SSD, so this is not a low-memory issue.

The issue happens even when sending very small prompts like “Hi”.

It is not related to project size or indexing.

Occurs even in a fresh or empty workspace.

This suggests the problem is not performance-related but possibly agent communication or extension host instability.

Internet connection is stable.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[Mobile_Dev]

Look at the below, where it is taking too much time. The cursor is nowadays a headache to use, as it badly affects our productivity.
It is almost taking 5min for simple prompt.

[deanrie]

Hey, this is a known issue with the extension host freezing. Try these steps:

1. Clear the workspace state database:

   • Fully close Cursor
   • Delete or rename this file: C:\Users\[your username]\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
   • Restart Cursor (you’ll need to sign in again)

2. Check if an extension is causing it:

   • Run cursor --disable-extensions from a terminal
   • If everything works, re-enable extensions one by one to find the one causing the issue

3. Run network diagnostics:

   • Cursor Settings > Network > Run Diagnostics
   • Are you using a VPN or a corporate proxy? If yes, try this: App settings Ctrl + , > search for “HTTP/2” > turn on “Disable HTTP/2”

4. If nothing helped, do a full reinstall (first remove any leftover state in %APPDATA%\Cursor).

Related thread with more context: Agent timeout within 16 seconds

Let me know which step helped, or if the issue is still happening.

[Mobile_Dev]

I basically uninstalled the cursor and then reinstalled it; now it seems good, but I encountered another issue, which is related to auto-apply. I don’t want to let cursor to change my files automatically without my approval. Like it was working fine before but when i reinstall the cursor, it’s making an issue now.
Please let me know how to disable the auto-apply of the cursor.

@deanrie

[deanrie]

Glad to hear the reinstall fixed the timeout issue.

What you’re describing with auto-apply is a known bug. The review UI (Accept/Reject per file) doesn’t render correctly after the agent makes changes. It’s not a setting you toggled. It broke in 2.5.x. A fix is already done and should ship in one of the next updates.

In the meantime, here are a few workarounds:

1. Use the Review button in the bottom-right of the chat panel to see all pending changes and accept or reject them there.
2. Run git diff after each agent run to track anything that got auto-applied.
3. Some users said downgrading to v2.4.37 helped. You can download older versions at Cursor · Download.

Main thread for reference: Only some diffs are shown when the agent makes changes Only some diffs are shown whhen agent makes changes

Let me know if you need anything else.

[Dragan_Vracar]

I had a same problem in archlinux, was stuck on 2.3.17 version for long time. Since there is no pacman package for it I used appimage wrapper to make proper installaton (cursor-appimage on aur.archlinux.org).
Discovered that using appimage itself worked with latest versions and started using it that way…
This morning tried different wrapper from aur.archlinux.org (cursor-bin) that converts deb package into pacman package, it works also…