Please keep 2.1.50 available — Agent hangs in newer versions after a few rounds

Hi Cursor team,

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.

Thanks.

It will look like this:

The thinking will take forever. Sometimes it is reading a file, but it will last forever, unusable.

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

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!