Cursor stuck on “Planning next moves” (troubleshooting already attempted)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor has been stuck on “Planning next moves” for an extended period and I haven’t been able to resolve it. I’ve seen similar reports from other users and tried the recommended troubleshooting steps, but the issue persists.
What I’ve already tried:
• Uninstalled/reinstalled Cursor (including downgrading: removed the newer version and installed v2.0)
• Restarted Cursor multiple times and rebooted my computer multiple times
• Network connectivity checks
• Cleared/disabled extensions and extension data
• Disabled installed MCP servers
• Switched models (Claude Sonnet → GPT-5.2 Agent)
• Other general debugging steps, with no change
This has been happening since about two weeks ago, and it’s blocking my work. Could you please help me diagnose and fix this?

Steps to Reproduce

Cursor version: 2.0.77 (user setup) on Windows_NT x64. when I type a question in the chat window, it stays stuck on “Planning next moves” for hours

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

2.0.77 (user setup) on Windows_NT x64

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey there!

There’s really not much troubleshooting that can be done on this version, and a lot has been improved lately (especially in the latest versions of 2.3).

Can you try downloading 2.3 from the downloads site. If it’s not working, sharing the request ID and logs is the best way to troubleshoot.

Same here I’m ex I’m experiencing the same behavior but on macOS

Plan mode doesn’t work
Mealy get stuck on questions When it tries to prompt the user

I am facing the same issue but it appeared for me after i upgraded to Pro. After that i couldn’t be able to use Cursor agent and every time its getting stuck on ‘Planning next moves’

got help from chatGPT and customer support service of Cursor, but couldn’t resolve the issue. later i changed network, working fine after that.