Cursor is now completely unusable

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is simply unusable now, so sad it is completely and utterly broken. using windows 11 fiber connection, and it just sits there and just spins planning next moves…it is beyond frustrating and I update to the latest version the second it comes out still nothing…I think the lead AIs now are bricking cursor on purpose it seems like.

Steps to Reproduce

Cursor is simply unusable now, so sad it is completely and utterly broken. using windows 11 fiber connection, and it just sits there and just spins planning next moves…it is beyond frustrating and I update to the latest version the second it comes out still nothing…I think the lead AIs now are bricking cursor on purpose it seems like.

Expected Behavior

TO CONTINUE THE CHAT!!!WORK

Operating System

Windows 10/11

Version Information

Version: 2.4.23 (user setup)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
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?

ALL MODELS

For AI issues: add Request ID with privacy disabled

Not attaching. Why the hell do you think all code can be made public at all times.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. We’re seeing similar reports from other users on 2.4.x. The Agent really does get stuck on “Planning next moves”.

Here’s what to try:

Quick workaround (worked for others):
Roll back to 2.3.41 or 2.3.34. A few users confirmed this fixes it. Download an older version from Download · Cursor.

If you want to stay on 2.4.23:

  • Run cursor --disable-extensions from the command line. If the Agent works, one of the extensions is blocking it. Turn them back on one by one to find the culprit.
  • Go to Settings > Network > Run Diagnostics. If anything fails, try switching to HTTP/1.1 in Network settings.

The team is aware of the issue. For now, the most reliable option is rolling back to 2.3.41.

Also, could you share the request ID (chat menu > Copy Request ID)?

Let me know if it helped.

1 Like