Latest version hangs on planning moves and waiting for terminal script responses

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

latest version hangs on planning moves and waiting for terminal script responses . it’s been a bane of my existence for some time and seems to be getting worse. every time I start a chat, it eventually hangs showing “planning moves” or it hangs because it can’t see the results of a terminal script it ran.

no effort on my part can get it kickstarted except to shut the app down or open new chat and paste in the last conversation from the other chat I had.

I’m running the claude api key for my opus 4.6 coding threads. on windows 11.

Steps to Reproduce

start a coding chat, let it evolve, eventually claude writes a script and tries to run it in its thread terminal and waits for a response
response never materializes, even if I paste response into thread, it eventually hits a “Planning Moves” state it never leaves.

Operating System

Windows 10/11

Version Information

Version: 2.4.28 (user setup)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Claude API opus 4.6

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue in 2.4.x. Quite a few users are seeing hangs on “Planning Next Moves” and problems with terminal responses.

A couple things to try:

  1. Roll back to 2.3.41 or 2.3.34. This is the most reliable workaround right now. A few users confirmed it fixes the issue. You can download it from Cursor · Download.

  2. Run without extensions. From the command line, run cursor --disable-extensions. One user fixed it this way, so it likely means one of the extensions is conflicting.

  3. Check indexing. Sometimes “Planning Next Moves” is blocked while the project is indexing. Make sure indexing has finished.

Also, can you confirm if this only happens with Opus 4.6 via BYOK, or does it also happen with Cursor default models? That’ll help narrow down whether the terminal hang is tied to the API key.

Let me know if any of these help.

Thanks. I’m looking into the ideas you suggested.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.