Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I am on v 2.6.18 and when Cursor is running, every Agent execution times out and my PC is painfully slow. I tried downgrading to a previous version, disabling extensions, cleaning cash, downgrading to previous version, and it’s still not working.
I did find two similar issues Cursor UI freezes up when agent is working and Cursor Pro Subscription Working but Agent Execution Timed Out and tried the suggested steps - they did not help.
Appreciate your help.
Steps to Reproduce
Install cursor 2.6.18
Open Cursor > PC freezes, agents do not execute
Expected Behavior
Agents work, other apps on my computer work
Operating System
Windows 10/11
Version Information
Version: 2.4.23 (user setup)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
For AI issues: which model did you use?
Tried different ones, they all timeout
Does this stop you from using Cursor
Yes - Cursor is unusable
first, not sure if i am missing something or not, but you said installed version is ‘2.6.18’ but your copy/paste version info says ‘2.4.23’, which seems off.. so maybe try updating again?
next, what kind of hardware do you have and are you using anything other than Cursor at the same time? also, to mention, it might (only might) be cache/storage issue because i encountered similar problem some time ago, but i resolved it by moving cache folder (and other related stuff) to different drive.
Hi Nadya,
This is a known issue we’re actively tracking. It’s client-side — your account/subscription are fine.
One quick note: you mentioned v2.6.18, but your version block shows v2.4.23 (after the downgrade). Either can be affected, especially since workspace state can persist across version changes.
Since you’ve already tried disabling extensions and clearing cache, here are the next steps (in the order most likely to help):
-
Close all chat tabs + start fresh - On Windows, some chat tabs (especially ones involving file changes) can balloon memory and freeze the whole IDE.
a. Close every chat tab
b. Open new chats going forward
c. If opening a specific chat re-freezes Cursor, delete that chat
-
Reset the workspace state DB - This is separate from the general cache and often fixes persistent hangs.
a. Fully quit Cursor
b. Delete/rename:
C:\Users\<you>\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
c.Relaunch Cursor (you’ll need to sign in again)
-
Update to the latest Cursor
Several Windows performance + stability fixes have shipped since 2.4.x.
-
Disable HTTP/2 (if not already)
Settings → search cursor.general.disableHttp2 → set to true → restart
-
Clean reinstall (last resort)
Reinstall Cursor after deleting %APPDATA%\Cursor(to remove all leftover state)
If it’s still happening, can you share:
Related threads which might be helpful to find workarounds & stay updated: Agent execution time-out & Laggy Chat
Best,
Mohit
I downgraded to 2.4.23 because I thought it might solve the problem. I dont have much running in parallel.
Hi Mohit,
Thanks for all these tips. I did follow all of the recommendations, and still having issues:
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: dc5b295c-4d59-4639-bdb2-c38014cc6a9d
{“error”:“ERROR_CUSTOM”,“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 vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43779:12719
at async gJy.createExecInstance (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43779:10479)
at async VxA (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34039:582888)
at async DJ.execute (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34240:6603)
at async sRu.execute (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43779:1323)
at async DNw.execute (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46852:2775)
at async X3u.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46862:3965)
at async X3u.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46862:5603)
at async X3u.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46862:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34305:17597)
at async Ea (vscode-file://vscode-app/c:/Users/W500239/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45787:4826)
Version: 2.6.18 (user setup)
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.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
I’m sorry this is still happening after all the troubleshooting you’ve already done.
I checked your request ID and can confirm that the timeout is occurring locally. Your requests are not reaching our servers at all, so this appears to be an extension host issue on the client side.
A couple of quick checks will help us narrow this down:
First, can you confirm whether you completed the clean reinstall from step 5 in my previous message?
Second, after the clean reinstall, please try opening Cursor with an empty folder instead of your usual project. You can create a new empty folder on your desktop, open it in Cursor, and then try running the agent there. This will help us determine whether the issue is tied to your workspace or to Cursor itself.
If the agent still times out in an empty folder after a clean reinstall, that would strongly suggest you’re a bug we’re tracking. In that case, I’ll escalate your case directly to our engineering team along with the diagnostic details.
One additional thing that would be very helpful for them:
Open Help → Toggle Developer Tools, switch to the Console tab, reproduce the timeout, and send me a screenshot of any red error messages that appear.
Hi Mohit,
I did clean-reinstall, and opened an empty folder while closing all other project folders as you suggested. Here is one a complete log. The agent did not time out of the second retry though. Third prompt really hang in the middle.
Thank you for going through the clean reinstall and empty folder test, and for sharing the console output. That was very helpful.
Since the issue persists in an empty folder after a clean reinstall, this confirms that this is the underlying bug we’re currently tracking, rather than something specific to your workspace or configuration. The intermittent behavior you described (where the second retry worked but the third prompt hung) matches what other affected users have been experiencing.
I’m escalating your case to our engineering team along with the console output and diagnostic details. They’re actively working on a fix.
In the meantime, retrying the prompt may help in some cases. If the agent times out, submitting the request again can sometimes succeed on the next attempt, as you observed.
I’ll update this thread as soon as there’s progress on the fix.
Best,
Mohit
1 Like
@mohitjain any update on the issue?
Thx
Unfortunately, there isn’t a fix available yet for this issue, but our engineering team has it as a top priority and is actively working on it.
In the meantime, I’d recommend updating to the latest version (2.6.21) if you haven’t already, as there have been some stability improvements since 2.6.18. You can check via Help > Check for Updates.
I’ll update this thread as soon as a fix is available.
Hey @Nadya_Hrebinka!
The agent execution timeout issue has been addressed in a recent Cursor update. Updating to the latest version should resolve this.
