Agent unusable after update

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor just stuck at Planning next moves after the update!

Steps to Reproduce

Just input whatever to the agent.

Expected Behavior

stuck at planning next movesS

Screenshots / Screen Recordings

Operating System

Windows 10/11
MacOS

Current Cursor Version (Menu → About Cursor → Copy)

v2.1.46
vscode v: 1.105.1

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. The Agent is stuck on “Planning next moves” - looks like a network or extensions issue.

Could you please share:

  • Request ID of the stuck request (Privacy Mode off) - in the chat menu on the right. How to get it: Getting a Request ID | Cursor Docs
  • Screenshot of the console during the hang (Help > Toggle Developer Tools > Console) - look for “ETIMEDOUT” or “unavailable” errors
  • Result of Cursor Settings > Network > Run Diagnostics

Quick checks:

  • Run cursor --disable-extensions in the terminal, open a new Cursor window, try the Agent in an empty project (no open repos) - if it works, it’s an extensions issue
  • Cursor Settings > Network > enable “Disable HTTP/2”, then restart
  • Try another model (Sonnet 4.5) - if it works, it might be related to Opus 4.5

Similar thread (resolved with extensions): SLOW or NO response from the agent

Share the details.

Mine often starts hanging in the terminal since update

So, I was (Opus 4.5 was) creating a download script for me to download model files from Huggingface. I noticed that when I pasted the link and it appeared in the context as an actual clickable link instead of plain text, Opus would try to download the model file before finishing the planning step.

So be careful what you link, and if in doubt, break the link (use the unlink command).

The terminal is broken in the latest 2 updates. Bets to request a credit refund, until the cursor resolves the issue.

2 Likes

Hi that is not true, downgrade back to v2.0.77 the agent started working again.

How to downgrade ?