Issue Report: Frequent "Planning Next Moves" hang in Cursor with Grok 4.5 High

Support Bug Reports
,
1

I am using Cursor with Grok 4.5 High, and it frequently gets stuck in “planning next moves,” which is unacceptable. I do not want to use API models for the time being, so please stop suggesting that I use an API; the same issue occurs with both AUTO and COMPOSER 2.5.

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hi @asf_safa!

Sorry you ran into this. Grok 4.5 has been experiencing temporary high-load periods this week, and the hang you saw was the client automatically retrying. This morning’s issue should now be resolved.

Please let us know if you continue to have any trouble!

8

Same here. Basically my team account is unusable. It’s not “resolved”. My API is at 100% so it may be related to that, a bug, cause my team members have no issue using Cursor.

9

The issue persists even today for me. Both in the IDE and the agents CLI. I’m on MacOS Sequoia

Version: 3.12.30
VS Code Extension API: 1.128.0
Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480
Date: 2026-07-21T22:50:03.568Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

AgentsCli: 2026.07.23-e383d2b

10

It’s the same situation again today; the first-party service is just very slow and keeps getting stuck on “planning next moves.” What on earth is going on?

11

If you have Request IDs you can share from affected chats, that would help a lot!

12

Colin here is one chat id that stopped working: 139ceea4-91db-4391-823b-7fa0c6a33de4

Any other chat I try basically it never created request id, seems like it never reaches the server. Both with cli and IDE.

I have successfully used cloud agents, both locally blocked 100%. Restarted, relogged in…

EDIT:
One more: 37c24efd-33f3-4524-b28f-36a67c1e6255

13

@igor_trmc Is this only affecting Grok, or all models? If it’s all models, it’s likely a Network issue (especially if the request never get to our backend), and Network Diagnostics should be your first stop.