Cursor is not usable currently.
planning next moves all day.
Is the team actively addressing this?
Cursor doesnāt work. Just says āPlanning next movesā indefinitely no matter what I do, what model I choose etc
Iāve just installed Google AntiGravity and get the exact same issue, could this relate VS code? No fix or anything from Cursor on this?
Version: 2.1.17 (system setup)
VSCode Version: 1.105.1
Commit: 6757269838ae9ac4caaa2be13f396fdfbcf1f9a0
Date: 2025-11-21T08:55:17.983Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Ok so I got mine working again, it seems the freezing is a Windows issueā¦
Multiplane Overlay (MPO) is a Windows graphics feature that offloads certain rendering tasks directly to the GPU.
- It improves efficiency, but recent Windows 11 24H2/25H2 updates (KB5068861) introduced regressions where MPO causes frozen or partially rendered windows in Electron apps (Cursor, Antigravity, VS Code, Discord) and even some native apps like Greenshot.
Registry tweak to disable MPO
Hereās the general process users have reported:
-
Open Registry Editor
- Press
Win + R, typeregedit, and hit Enter.
- Press
-
Navigate to the graphics driver key
Code
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm -
Create a new DWORD value
-
Name:
OverlayTestMode -
Type:
REG_DWORD -
Value:
5(this disables MPO)
-
-
Restart your PC
- Changes only take effect after a reboot.
After this Cursor which would process one prompt and lock up 90% of the time is now working again, AntiGravity which would not even starts without locking up now starts every time.
Thanks for sharing this! Downgrading to 1.6.46 worked for me too ā the agent finally stopped freezing at āPlanning next moves.ā Really hoping this version stays stable and I donāt run into more issues down the line.
Hi James44, any progress on your problem ? I have the same for the past 24 hours nowā¦. wonder if I should continue paying for Cursor ? not the first time I have a problem.
19 posts were merged into an existing topic: Planning next moves stuck