My chats are just hanging with "Planning next moves" and "Taking longer than expected..."

deanrie · April 6, 2026, 7:23pm

@Casey_Salmon your diagnostics look clean, so it’s not a network issue.

In Settings, where you see the HTTP/1, HTTP/1.1, HTTP/2 options, select HTTP/1.1 and fully restart Cursor. The main workaround is to switch from Auto to a specific model like Claude 4.6 Sonnet or GPT-5. Auto uses routing that sometimes gets stuck.

Also, please send:

Cursor version Help > About
OS
Request ID from the stuck chat right top corner menu > Copy Request ID

The every 3 to 4 hours pattern is interesting. With the Request ID, we can check what’s happening on the server side.

Casey_Salmon · April 6, 2026, 7:30pm

so lets pretend im broke and can only afford auto do i just switch the model then switch back or do i need to run a basic command then switch back?

deanrie · April 6, 2026, 7:42pm

No, you don’t need to switch models back and forth. If it freezes, just open a new chat with Cmd+N or Ctrl+N and try again. That often helps, especially if the issue is looping like yours.

For HTTP, in that list (HTTP/1, HTTP/1.1, HTTP/2) pick HTTP/1.1 and fully restart Cursor. That’s the workaround instead of Disable HTTP/2.

I still need the info from the last message too: your Cursor version (Help > About), your OS, and the Request ID from the frozen chat (menu in the top-right of the chat > Copy Request ID). Without the Request ID, we can’t check what’s happening on the server.

Casey_Salmon · April 6, 2026, 8:24pm

ok yes i have done this, ive had up to 4 agents trying, when it hits the “taking longer than expected” spot it effects all agents, even older ones that were running smooth, its a full on halt to the agents. Mine just started doing it again FYI so the 3-4 hours thing i was incorrect about.

Casey_Salmon · April 6, 2026, 8:43pm

20 minutes, deadlocked, no agents working

Casey_Salmon · April 6, 2026, 8:54pm

and it just started moving at a turtles pace and now its duplicating markdowns and jacking up what i had… this needs to get fixed or it will break some repos - for whats its worth, all of the agents that halted, resumed at the same time no new agent creation needed to run what was pending…

Casey_Salmon · April 8, 2026, 3:19am

yall… this is still going on, this is not on our end….

Alex_Shavkuta · April 12, 2026, 7:41am

Hi, are there any updates according the issue? Im still getting a timed out error when running agents on a worktree.

Im running Opus 4.6 High(not in Auto mode)

This is my systems info:
Version: 3.2.0-pre.11.patch.0
VSCode Version: 1.105.1
Commit: 162121a60ddf638794d208fc9fb045a0dd019840
Date: 2026-04-11T05:50:37.024Z
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0
This is my Request IDRequest ID: 78ba8ad8-9b77-4b03-93cd-2f6b46464f5f

This is the error
{“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 vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38250:27228
at async tdS.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38250:23698)
at async O4_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28645:632085)
at async DF.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28866:7896)
at async pgd.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38250:1792)
at async bzS.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41245:4969)
at async sxd.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41255:4190)
at async sxd.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41255:6959)
at async sxd.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41255:17838)
at async M3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28983:16809)
at async JiC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44633:83361)
at async twC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45654:12554)

deanrie · April 12, 2026, 2:37pm

I can see the issue still reproduces in worktree mode. Thanks for the Request ID and the detailed stack trace.

The ERROR_EXTENSION_HOST_TIMEOUT or deadline_exceeded error in worktree is a known issue. The team is aware. There’s no ETA yet, but your report helps us prioritize it.

A few things to check:

You’re using Opus 4.6 High thinking with a 1M context window. Try temporarily reducing the context window, or switch to standard thinking. A large context in worktree can cause the extension host to time out.
Make sure your worktree doesn’t contain too many files outside .gitignore. Codebase indexing in a worktree can overload the extension host.
You’re on nightly 3.2.0-pre.11. If possible, try stable to rule out a nightly-only regression.

I’ve logged the Request ID. Let me know if any of this helps.

deanrie · April 12, 2026, 2:45pm

I can see the issue is still happening. The fact that all agents freeze and then resume at the same time points to a server routing issue, not something local.

But to check server logs, I need a Request ID. Without it, we literally can’t find your requests on the server. Next time an agent freezes:

Click the menu in the top-right of the chat > Copy Request ID
Send it here along with your Cursor version via Help > About and your OS

Also confirm this: did you switch HTTP version to HTTP/1.1 and fully restart Cursor, not Reload Window, but Quit + Open?

Alex_Shavkuta · April 15, 2026, 7:49am

Im still getting the same issue, here is what i tried:

Running Opus with medium thinking and 200K context window.
Downgrading to a stable version of cursor
Running with a Different model(Codex 5.3)

One time it did log some actions it did but then timed out again(couldn’t reprduce it again)

This is cursor Info:

Version: 3.1.14
VSCode Version: 1.105.1
Commit: d8673fb56ba50fda33ad78382000b519bb8acb70
Date: 2026-04-14T01:39:23.679Z
Layout: editor
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 25.3.0

This is the Request Logs:

Request ID: fc919e0b-01a7-4343-800f-03a20fa1ce16
{"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 vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38248:27166
    at async VlS.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38248:23636)
    at async JF_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28649:630571)
    at async BF.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28870:7917)
    at async Vpd.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:38248:1792)
    at async NHS.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41243:4969)
    at async Mkd.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41253:4190)
    at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41253:6959)
    at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
    at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
    at async itC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44636:94910)
    at async tbC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45657:10206)
    at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:42916:88493

Shubham_Singh · April 15, 2026, 1:11pm

I am also getting same network issue:

Request ID: d3e96c20-c17d-4c6e-93bc-6689d0d4a6ec
[internal] Blob not found
oae: [internal] Blob not found
at iz_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.runAgentLoop (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:11960)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Object.Ra [as onSubmit] (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)
at async vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40235:100561

deanrie · April 15, 2026, 2:46pm

@Alex_Shavkuta

I can see you’ve tried all the workarounds, lowering thinking and context, switching to stable, and changing the model. It’s really frustrating that none of that helped.

A few things to check while we don’t have a fix yet:

How big is the project in the worktree? Do you have a lot of files outside .gitignore? A large index can cause timeouts.
Try disabling extensions. Launch Cursor from the terminal with cursor --disable-extensions and see if the issue still happens. If it doesn’t, one of the extensions is overloading the extension host.
If you can, try the worktree on another small repo. We need to confirm if it’s tied to this specific project.

Let me know what you find.

deanrie · April 15, 2026, 2:49pm

@Shubham_Singh

You’re hitting a different error, Blob not found, so it’s not the same as the thread above. I’ll need a bit more info:

What Cursor version are you on? Help > About
What OS are you using?
What exactly were you doing when it showed up, agent mode or ask mode?
Does it reproduce every time, or was it a one-off?
Cursor Settings > Network > Run Diagnostics, please share the results

Shubham_Singh · April 15, 2026, 3:13pm

@deanrie

What Cursor version are you on?
3.1.14

What OS are you using?
ubuntu 22.04

What exactly were you doing when it showed up, agent mode or ask mode?
I updated today, and asked one coding assignment in agent mode.

Does it reproduce every time, or was it a one-off?
I encountered it first time today

Run Diagnostics,

deanrie · April 15, 2026, 4:02pm

@Shubham_Singh

All diagnostics look good, your network is fine. The Blob not found error is on the server side, not on your end.

Since it only happened once, it was most likely a temporary backend issue. Try this:

Open a new chat with Ctrl+N and run the same prompt again
If it keeps happening, try a different model for now

If the error comes back, send a new Request ID from the failed chat and we’ll check it on the server side. The team is aware of this type of error.

Chauhan_Sahil · April 16, 2026, 11:55am

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I try to use models like Sonnet 4.5, Gemini 3.1 Pro/Flash, Grok, all is working extremely slowly showing “Taking longer than expected…” and then gives output and then when it gets to Planning again, then again “Taking longer than expected…” for 2-3 minutes for each Planning, working extremely slowly, completely unusable.

Steps to Reproduce

Select any AI Model as mentioned and send a request, takes so much time to give output.

Expected Behavior

Should work instantly without showing “Taking longer than expected…” specially for almost all ai models.

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Sonnet 4.5
Gemini 3.1 Pro
Grok 4.20
Sonnet 4
Composer 2 (Sometimes work sometimes not)

For AI issues: add Request ID with privacy disabled

N/A

Does this stop you from using Cursor

Yes - Cursor is unusable

Chauhan_Sahil · April 16, 2026, 12:24pm

PS: I already tried running in a complete empty folder project, also Ask mode too, and cloud agent too, same issue, also tried in my two different macs, same issue, so its definitely not something from my side issue.

PS C:\Windows\system32> (Get-Item “$env:APPDATA\Cursor\User\globalStorage\state.vscdb”).Length / 1MB
24804.8515625
PS C:\Windows\system32>

deanrie · April 16, 2026, 12:53pm

@Chauhan_Sahil

24,8 GB, that’s the reason. A normal state.vscdb is tens of MB, maybe a couple hundred at most. Yours is about 100x larger than normal. Cursor reads this file on every request, so you get delays on all models.

Fully close Cursor, not Reload Window, but Quit. Then in PowerShell:

Copy-Item "$env:APPDATA\Cursor\User\globalStorage\state.vscdb" "$env:APPDATA\Cursor\User\globalStorage\state.vscdb.bak"

Then install sqlite3 if you don’t have it:

winget install SQLite.SQLite

Then clean it:

sqlite3 "$env:APPDATA\Cursor\User\globalStorage\state.vscdb" "PRAGMA journal_mode=DELETE; BEGIN IMMEDIATE; DELETE FROM cursorDiskKV WHERE key LIKE 'agentKv:%'; DELETE FROM cursorDiskKV WHERE key LIKE 'bubbleId:%'; DELETE FROM cursorDiskKV WHERE key LIKE 'checkpointId:%'; COMMIT; VACUUM;"

Note: this will remove chat history from the UI. Transcripts will still be in ~/.cursor/projects/. After that, open Cursor and check the file size again, it should drop by a lot.

Let me know if it helped.

Yaroslav_Zhuk · April 17, 2026, 8:25am

Dean Rie, I think I’ve found a solution to the problem. I had the same issue, and none of the fixes worked for me (I went through all the discussions). My diagnostics were fine, and disabling HTTP2 didn’t help.
Then I tried disabling external skills—and voila, everything started working. I suspect they were causing overlaps or conflicts. But this fix REALLY solved it. I’d been struggling with this problem for a whole week.

The FIX is to turn off this mf:

Topic		Replies	Views
[Cursor 2.5/2.6] Taking longer than expected Bug Reports chat , performance	82	23814	April 7, 2026
Planning next moves stuck Bug Reports java	393	25950	February 11, 2026
Planning next moves / Taking longer than expected Bug Reports	9	293	June 23, 2026
Cursor takes to long to response Bug Reports chat , networking	13	382	September 10, 2026
Stuck at "Taking longer than expected" Bug Reports chat	58	2859	October 21, 2026