Constantly stuck in "Planning Next Moves" or "Generating..."

Ideas Feedback
, ,
1

In more recent versions of Cursor, the amount of time spent in “Planning Next Moves” or “Generating…” has jumped dramatically. An exhorbitant amount of time, is now spent in those modes, rather than the agent actually doing anything useful and progressing through the task at hand.

The problem now seems to be even worse, where I get completely stuck in “Planning Next Moves”, and am unable to get out of it short of killing Cursor entirely. This is starting to have such a dramatic effect on productivity, that instead of the agent improving productivity, is is beginning to hamper it.

There is a severe lack of insight into what Cursor is doing during these cycles. Unlike a “Thinking” cycle where you can see what the model is doing, a “Planning Next Moves” or “Generating…” entry cannot be expanded, and is a complete and total BLACK BOX. Similarly, context usage, is a complete and total BLACK BOX. This lack of insight is starting to seem like a Cursor issue….competitors are starting to give devs clear insight into these aspects of the agent now, and I think that is critical.

I have no idea, why Cursor is a dead duck right now. Its been sitting in “Planning Next Moves” for over 5 minutes, and I honestly don’t know if it is actually doing something, or if it is totally hung and is going to require me to kill Cursor and restart it from scratch (a totally UNACCEPTABLE situation!) I am just stuck here, waiting on a thing that Cursor is showing me ever more often, sucking up and wasting time, where I have NO RECOURSE, and just HAVE TO WAIT.

This is a terrible problem. First, WHY is it taking so freaking long nowadays, whenever Cursor hits these points? Second, WHY is this occurring so freaking often now? Seems to happen WAY more than it used to in the past. Third. WHAT exactly is going on when these indicators appear??? What? I’ve been wondering that since I first started using Cursor…what the heck does “Planning Next Moves” mean? What’s going on? Why does it take so darn long? The fact that this seems to appear every five minutes or so now, and I am just STUCK waiting for it to clear, IF it clears, has become absolutely infuriating…

9 Likes
Issue: "Connection stalled" and "NGHTTP2_ENHANCE_YOUR_CALM" errors in large monorepo
Prompt doesn't start
3

Same issue. I’ve tried to reboot, reinstall, kill the index, remove extensions, etc. Nothing works. And the diagnostic tool shows all is working great. Two days of zero productivity now.

4

Same issue here. The product is becoming unusable because of this. And I do not see a response from the company. Do we need to generate multiple reports with the same issue so we get some response?

5

Same issue here, I’m on MacOS and I cannot use plan mode on any project right now. It starts to plan, then gets to the draft section and then it locks up completely, I have to kill cursor and start over, tried it on various projects small or large and every one does the same thing.

I reinstalled - did not fix. On the primary build release. v2.4.21

image
image610×244 9.55 KB

6

I’m facing the same issue!

7

Same issue

Agent mode works fine, but plan always crashes cursor, regardless of project, or size of project
Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
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.2.0

8

Same issue.

Version: 2.4.21 (user setup)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
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

9

Rolling back to

Version: 2.3.41

works as a short term fix

Latest version hangs on planning moves and waiting for terminal script responses
Cursor Agent stuck in 'Planning Next Moves'
10

I myself ended up going back to 2.3.34. From 2.3.35 onwards, there were increasing issues with the agent terminals. By 2.4, the agent terminals were beyond broken and there were severe agent issues in general.

There seem to have been some ill-vetted major changes to both the agent and the way the agent manages terminal instances, or some monster regressions. Either way, anything beyond 2.3.34 for me seems to be unusable.

Really wish that the Cursor team would learn that just because you are vibe coding, does not mean you ditch all necessary and essential validation checks before you release new code!

11

Already follow up this case with Cursor Team. Cursor team aware this problem and become Top Priority for solving this issues.

Also, for better helping Cursor Team Debugging, Alongside the Req ID(Disable Privacy first), it’s super helpful if you can open > Developer: Export Logs... and select Main, Window, Extension Host, Extension Host (Remote), Remote - SSH, last two only if Remote SSH is used.

1 Like
13

The need to disable privacy violates my companies policy, so that pretty much negates the ability for me to share request ids (I mean I can, but, privacy will be enabled.) Not much I can do there.

14

How about this log?

open > Developer: Export Logs... and select Main, Window, Extension Host, Extension Host (Remote), Remote - SSH, last two only if Remote SSH is used.

16

Hey guys I just tested on 2.4.22 Early release build and its no longer an issue for me.

image
image744×916 70.9 KB

17

I’m seeing the same issue. When it edits multiple files at the same time, it sometimes doesn’t apply the changes to the corresponding files and just gets stuck. Even after waiting for hours, it doesn’t progress unless I kill or stop the process and then tell it to resume.

This happens especially when the context or chat gets fairly long. With Cursor 2.5, it actually feels worse—sometimes the progress bar shows that only about half of the context is used, yet it still takes a very long time. However, if I start a new conversation, it runs normally again. intrestingly the last 2.4 update seems fix the waiting or planning for significant amount.

18

if you still get this problem,

you can share your Request ID with Developer Log

Constantly stuck in "Planning Next Moves" or "Generating..." - #11 by Naufaldi_Rafif

19

sometime it get stuck for very long time (even after a few hours still no progress).

so when it seems get stuck, I manually stop it, then send the chat message again.

seems the error handling or network connection timeout can be improved

20

I’m still getting this issue on 2.4.22 - it frequently gets stuck on “Planning next moves”.

Not sure if this is the exact same issue, but it’s also become stuck several times trying to extract a few hundred lines from a large file (~33MiB, used to work fine). Several requests have stalled and used millions of tokens, costing a lot with no actual result.

Sometimes it eventually times out, e.g. on macOS:

Request ID: c1890554-062b-44be-bf57-daf953093f5e
Connection stalled
LTe: Connection stalled
at rpf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4764)
at fva.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async Hyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34196:57047)
at async Zpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:7695)
at async Zpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Ei (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)

21

same issue here… it stucks forever.. it doesn’t start generating..

and why is cursor doeing nothign about it, even posting in this forum…

22

I’m just getting this issue with the below version:

Version: 2.4.27 (user setup)
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
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.22631
24

i found a solution… which is not really solution… but it works for now…

in the moment i disabled all MCP-Servers with error-state, the Agent chat was working again…

so it seems, like faulty MCP-Servers block AI working on something…

it would be nice, if Cursor team finds a solution for this… like not using faulty mcp-servers or a hint for it…