Agent is stuck on "planning next moves"

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

existing and new agent chats are not responding. stuck on ‘planning next moves’. model is opus 4.5.

Steps to Reproduce

ask the agent to do anything. create a new chat and ask agent to do anything. moel is opus 4.5.

Expected Behavior

agent should start acting and answering.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.7 (user setup)
VSCode Version: 1.105.1
Commit: ca0f9bf806f235ea014a22712cbcbf5e88ca77e0
Date: 2026-01-20T20:52:38.077Z
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.22631

For AI issues: which model did you use?

opus 4.5
composer 1

For AI issues: add Request ID with privacy disabled

ff07054b-b102-4ce5-8d6d-ae83ea5ac992

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
3

Hey, thanks for the report

Let’s try step-by-step diagnostics:

  1. Network Diagnostics (start here)
    Settings > Network > Run Diagnostics. If anything fails (DNS, HTTP, SSL) - that could be the issue. Are you using a VPN, corporate network, or antivirus?

  2. Try disabling HTTP/2
    Settings > Network > HTTP Compatibility Mode > HTTP/1.1. This is especially important for corporate networks, VPN, or Zscaler.

  3. Disable all extensions
    Run from command line: cursor --disable-extensions. If Chat starts working, then some extension is blocking it. Enable them one by one to find the culprit.

  4. Check indexing
    Look at the status bar in the bottom right - is indexing running? A few users had the agent hang because indexing was blocking it. One user fixed it by updating to version .35.

  5. Try a different network
    One user fixed it by switching Wi-Fi or hotspot.

If nothing works, please share the Network Diagnostics results and a screenshot from Developer Tools (Ctrl+Shift+P > Developer: Toggle Developer Tools > Console). Let me know if there are any red errors there.

Similar threads with more solutions: