It seems like downgrading will solve the problem.
I tried it several times:
5. Now I downgraded back to 2.2.44 and it’s working.
(HTTP2, custom base URL)
hi,
Chat is broken in Cursor 2.3.* on macOS (arm64).
Chat mode hangs on “planning next moves” and errors with
[any model] No first token received within 10s.
Issue persists after:
resetting user settings
disabling all extensions
testing in a clean workspace
network test is ok
clean all app related cache
Works fine on 2.2.* → regression in agentic-composer / chat service in 2.3.*.
Are you stumped by the bugs you’ve written yourself? Is this problem really that difficult to solve?
Hey all.
If you’re still getting stuck on Planning Next Moves, please make sure you include a Request ID when you post. It really helps us track down the remaining issues.
I am still stuck since past 18 hours 7298ff71-308b-4c88-b87c-fab01826d4a2
I still have this problem, even after deleting the cache in the AppData\Roaming\Cursor\User\workspaceStorage file. It’s really infuriating.
It started working fine after restarting with a new agnet, but it’s very unstable.
in my case it looks like some network proxy settings have changed and now Chat and Agent items are failing the network diagnostics:
lowering HTTP compatibility to HTTP/1.1 seems to “fix” it for me:
I’m dealing with the same issue… stuck on “Planning next moves”.
It’s happening right now, so I’m including the current request ID as well.
Request ID: c8044301-abd7-4ade-9a70-85deb365db59
{“error”:“ERROR_TIMEOUT”,“details”:{“title”:“Request timed out.”,“detail”:“Timeout waiting for next item.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Version: 2.3.35 (user setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Since this started happening a few days ago I get about one run in a chat session. Once I run a code test and come back to the chat to respond, it is stuck in “Planning next moves”. Then I export the chat transcript, close Curor, delete session folder from “C:\Users\\AppData\Roaming\cursor\User\workspaceStorage\”, reopen Cursor, delete the index and rebuild it, open a new chat, then drop the path to my exported chat history and ask it to review and continue.
I have only have 88 files in my index.
Using GPT-3.5 Codex High model, but issue occurs regardless of model.
Received an upgrade to v2.3.41 but issue persists.
Request ID: c0738e5a-3799-4d94-952f-3d9b8cd855b6
{“error”:“ERROR_TIMEOUT”,“details”:{“title”:“Request timed out.”,“detail”:“Timeout waiting for next item.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Version: 2.3.41 (user setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
after updating to v2.3.41, it seems to be working now
From what I found is that if HTTP 2 is relatively unstable regardless of the IDE version. I have found HTTL 1.1 to be more stable, for all who are still stuck, try to change HTTP mode to 1.1 from Network in settings.
Still happening even today.
Is this company dead or what? Months to fix simple regressions. This is not sustainable lol
I am facing the same issue. Can´t use it for days.
It does work though, when no project is selected. So probably the indexation is broken.
Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
Fresh Context has worked! Thank you very much!!
I have downgraded to version 2.0.77 and that seems to be working finally. I have it set to launch as admin to keep it from updating automatically.
Version: 2.0.77 (user setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
I have the same issue, started happening suddenly today.
Request ID: db997973-475d-4afa-8994-3cb207a34f6c
ConnectError: [unknown] Network disconnected
at dou.$streamAiConnect (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12706:472564)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:566:27936
at async HDs.toolWrappedStream (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9193:28813)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:10283:8983
at async KA.handleStreamComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9078:993)
at async TCo.streamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13689:12943)
at async j0o. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13835:9894)
at async K0o. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13837:2274)
at async M0o. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13826:1263)
at async F0o. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13826:31935)
at async hBe. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9193:49317)
at async z0o. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:13835:8947)
at async rBe.processCodeBlocks (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9131:4291)
at async wY.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:10283:11573)
at async Ba (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12585:3831)
Version: 2.3.41 (Universal)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
I also couldn’t resolve it by restarting the app.
However, although it’s not a fundamental solution, I was able to resolve it by logging out of my Cursor account and logging back in.
The situation when this bug occurred was that I was using Remote-SSH in Privacy Mode.
I’ve tried everything you suggest I can try, but it still gets stuck at a certain step.
Version: 2.4.22 (user setup)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
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.26200
Same Issue!!
Version: 2.4.23
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z (4 hrs ago)
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: Darwin arm64 25.3.0
