Planning next moves stuck

解决很简单,你只需要把项目文件重命名,然后重新打开项目就好。一个项目搞久了cursor会出现大量垃圾文件导致索引时出现灾难性问题。

Same here. Since 3 days Cursor is unusable. It takes either ultra long for any agent reaction (5-10 min) or freeze completetly in “Planning next move”.

I hope the issue will be solved soon and we get refunded for that outage.

This is pretty serious, not only you guys are not making any money if we are only prompting 5 times an hour and the rest of the time we are watching Youtube Shorts to prevent us from spamming the forum with complaints, the fact that this is a 100% blocker issue, and it effectively disables the product, you are losing 50% of all users affected. They will never come back. They will find a working product. They will forget.

Stop adding fluff and cruft to the interface that uses tons of CPU and RAM while doing nothing at all and fix the core product, let the people discover the tools and efficient workflows and help them spend more money. If the product is broken, features don’t matter.

You can see many requests that consume 0 tokens. This is when the cursor gets stuck!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I cannot get this message to go away, tried to rename WS, switch models, quit + reopen etc.

Steps to Reproduce

I just need to open the ide and try to chat…

Expected Behavior

I should get a response from the model

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
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

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

2.1.50 is the last version that worked for me. Thankfully, I still have it and can load it up and it works just fine. Any version after 2.1.50 is broken for me. Never loads user rules, network diagnostics just stays stuck spinning on DNS, HTTP/2, and SSL. Tried disabling HTTP/2, restarted, still doesn’t work. Network diagnostics stays spinning on DNS and SSL.

If I run network diagnostics in 2.1.50, it works instantly and flawlessly, even with HTTP/2.

Seems like the application just cannot connect to anything anymore on these newer versions. Tried wiping out my ~/.cusror, ~/.config/Cursor, and ~/.cache/Cursor directories. Got launch/sign in wizard, when through that, then it just hangs on loading at the end. Restarting just pops the wizard over and over again, and can never complete on the newer versions.

3 Likes

This issue happens within a few days ago, every now and then. After I switched to Pro+ plan, to speak frankly, it gives me bad experience.

I have to use Winsurf/Trae again, when I am waiting in *planning next moves…*

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent mode is taking too much time to respond, sometime it is taking like 15-30 minutes to respond.

Steps to Reproduce

Select agent mode, select any model you want, ask a question.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

2.2.20
b3573281c4775bfc6bba466bf6563d3d498d1070
arm64

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

2.2.27 (grabbed from the downloads page, as the application was saying there was no update available), works for me.}

EDIT: Nevermind. After restarting it a few times, not having changed anything or even edited any files, it now is broken the same way again.

same issue, stuck in planning next moves for minutes still. I would gladly move to Windsurf or Claude Code but i have a yearly subscription(

reporting same issue
started today all of a sudden

restarting did not resolve

seems there is more than a small issue

Yes - downgraded and the problem went away.

Makes it sound like bollaks when Cursor Team blames anything BUT their current version.

1 Like

Well, canceling my Ultra subscription today. We have had 6 updates since I have had this happen, and not a single one has resolved the issue. I cannot justify continuing to spend money on this when I spend more time troubleshooting the IDE than I do in getting actual work done.

3 Likes

Done with this battle with Cursor IDE, at least half of the recent requests couldn’t get through due to all kinds of reasons, and cursor team is not responding at all. Just unsubscribed, back to Claude code and other cli tools.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It keeps freezing after recent update in 2.2 and even in Downgrade version of 2.1

Steps to Reproduce

Ask any questions and it will stuck up

Expected Behavior

It should immediately show response or working it is performing like thinking.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.107.0 (user setup)
Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622
Date: 2025-12-10T07:43:47.883Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

default, sonnat 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It started recently, couple day ago. After working inside conversation on 79.1K tokens this time, Agent stops in the middle of conversation on Planning next move and nothing helps. I tried restarting IDE, restarting computer, installing today update. Nothing helps. Since yesterday every conversation stops in the middle. Each time i have to start new conversation and in the middle it stops too.

Steps to Reproduce

Just talk to agent. nothing else. and after around halp of the conversation it losts it.

Expected Behavior

Answer.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (system setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
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.26100

For AI issues: which model did you use?

Sonet 4.5, opus 4,5 after lost even Gemini 3 can’t connect again. Stops on Planning.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I prepare a prompt in Cursor and submit it, Cursor behaves as if no prompt was sent. There is no response, no processing indicator, and no output generated. The system simply returns to an idle state.

Steps to Reproduce

Open Cursor
Prepare a prompt (any length or content)
Send/submit the prompt
Observe that no action is taken

Expected Behavior

Cursor should process the submitted prompt and return a response or at least show a processing/loading state.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.36 (user setup)
VSCode Version: 1.105.1
Commit: 55c9bc11e99cedd1fb93fbb7996abf779c583150
Date: 2025-12-18T06:25:21.733Z
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

For AI issues: which model did you use?

Automatic

Does this stop you from using Cursor

Yes - Cursor is unusable

I’ve experienced the same issue, but it only appeared in some of my Dev Containers. When I used Cursor without a container, it worked fine. (This took me some time to figure out since I mainly work in Dev Containers.) However, as soon as I reopened a long-standing workspace in a container, the DNS, SSL, and HTTP2 diagnostics in the settings kept loading indefinitely. Meanwhile, agents were stuck in “Planning next moves.” Deleting the dev container in Docker and rebuilding it resolved the issue for me.

Cursor is literraly unusable… heh, i will no longer pay for it

Ok for now worked for me going back from HTTP 1 to 2.0 it resolved issue for now, i don’t know for how long.