If Cursor's agent sits on Planning Next Moves for minutes, your project is usually fine — this is most often a model-side delay. In the public forum thread, a Cursor staff member replied that a specific model (Grok 4.5) "has been experiencing temporary high-load periods this week."
Try first: switch the model
If the hang repeats with one model, pick a different model in the chat input and resend the same request. Per forum reports the hang clustered on Grok 4.5 High while other models responded normally. If you use Auto mode, explicitly pinning a model is another way around it.
Check the status page
Look at status.cursor.com for model or service incidents. If there is one, waiting beats changing settings. If there is none and the stall continues, run Developer: Reload Window and start a fresh chat — very long conversations can make the planning stage heavy.
Good to know
There is no confirmed official fix yet. User reports continued after the staff reply, so if it recurs, adding your Cursor version, model, and timestamps to the public thread helps. Until then, "switch model → check status → new chat" is the most realistic path.