Could you please keep Cursor 2.1.50 available as a downloadable option (or add an “LTS/stable” channel)? For my workflow, Agent is usable in 2.1.50, but every version after 2.1.50 eventually becomes unusable.
Issue: In newer versions, the Agent gets stuck indefinitely at “planning next moves” after the conversation runs for a few rounds (i.e., after several back-and-forth steps). Once it enters that state, it never recovers and the session is effectively dead.
This makes updating risky because I lose the ability to use Agent at all. I understand you may need to gate features for security or backend compatibility, but right now the result is: update → Agent hang → forced rollback.
If there’s a known workaround (e.g., a specific setting, network toggle, or cache reset), I’m happy to try it and report back. But in the meantime, please consider keeping 2.1.50 accessible for users who need a reliable fallback.
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!