Stuck in Planing next moves

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

the agent was stuck in the Planing Next Moves. This issue appears across multiple conversations and is not limited to a single project.

Steps to Reproduce

I have been encountering frequent issues with Cursor over the past few days: agent conversations keep getting stuck at the Planning next moves stage. This problem persists even when I start a new chat or restart Cursor, and it does not seem to be a network-related issue. It has lasted for nearly a week.
I learned from a forum and verified that deleting the contents inside AppData\Roaming\Cursor\User\workspaceStorage prevents this bug from occurring when Cursor launches and initiates a conversation the next time. This workaround works temporarily, yet the conversation gets stuck again after just one chat session. To resolve the freeze, I have to close Cursor and delete the files in that folder all over again.
The conversation ID where this issue most recently occurred is 7356c49b-f302-489a-b678-1ec3a7c8ee59. I hope the Cursor team can fix this bug as soon as possible. Additionally, if such errors arise on my end, I expect the Cursor client to indicate the root cause instead of leaving me waiting indefinitely. For your reference, I have not configured hooks, so this is not related to stop hooks.
This bug triggers much more often in the agent interface, while it occurs less frequently within the IDE (though I am not sure if this is merely a coincidence). The above text was translated using an AI translation tool.

Operating System

Windows 10/11

Version Information

Version:3.12.30(user setup)
VS Code Extension APl: 1.128.0
Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480
Date: 2026-07-21T22:50:03.568Z (3 days ago)
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium:144.0.7559.236
Nodejs: 24.15.0
V8:14.4.258.32-electron.0
xterm.js:6.1.0-beta.256
OS:Windows_NT x64 10.0.26200

For AI issues: which model did you use?

auto

For AI issues: add Request ID with privacy disabled

7356c49b-f302-489a-b678-1ec3a7c8ee59

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report and the Request ID, that really helps. The freeze on “Planning next moves” is showing up for a few users right now. It’s a known issue on our side and we’re tracking it. No exact ETA for a fix yet.

For a workaround, deleting workspaceStorage is a bit too extreme since it wipes state for all workspaces, so let’s try a less painful option:

  • When the chat freezes, run Developer: Reload Window via Ctrl+Shift+P, then Reload Window, instead of fully restarting.
  • If a specific chat stays stuck, start a new chat and pull context in via @Past Chats instead of clearing workspaceStorage. The freeze is usually scoped to a single chat, so a fresh chat fixes it in most cases.

Let me know if Reload Window helps, and whether a new chat freezes the same way. That’ll help narrow it down. Also, if you catch another example, please send the Request ID for the stuck request.

8

I’ve tried reloading the window as you suggested, but it didn’t work at all. When I resend the message, it still gets stuck at Planning next moves.

9

Hey, thanks for trying this and letting us know. One important thing: if you hit resend in the same chat that’s already stuck, it’ll very likely stay stuck. The stuck state is usually scoped to one specific chat, not all of Cursor.

Try this:

  • Open a completely new chat, not resend in the old one.
  • Pull in the context you need via @Past Chats, and reference the previous conversation.
  • Send your request in this new chat.

If the new chat also gets stuck on “Planning next moves”, please send the Request ID for that stuck request right from that chat (top right chat menu > Copy Request ID). That’ll help us see if it behaves differently from the previous case.

This is a known issue, not just you, and we’re tracking it on our side. I can’t share an exact ETA for a fix yet.