I am still getting the issue after the update as well. Changes are still not showing. Version: 2.5.25
I downgraded to version 2.4 and it’s working for now, but I hope it gets fixed soon.
The issue persists even in version 2.5.25. This specific feature is the only reason we choose Cursor over Claude Code. Please understand that this is a critical issue for Cursor.
Also 2.5.25. This is so annoying. Hope Cursor can fix this asap.
I can’t believe these (many) guys together with the best AI agents were not able to fix this bug!!!
WTH is going on??? ![]()
This should have been fixed in 1 hour!
It makes me wonder if there is any state involved on this (like gag order)
It is on the interest of whom to apply changes on our files without our review?
After seeing what the Pentagon is doing with Anthropic, this thought may not be that crazy
Same problem here. This is very very annoying, it’s the main advantage Cursor has and why I chose it personally and for our company. We need this FIXED ASAP.
I’ve switched back to 2.4 because I just can’t work.
Nope, not fixed. Had to roll back to 2.4 because this is unusable.
no .. still not fixed.
Can some post a screenshot of the issue in 2.5.25 in order to accelerate a final fix.
Worse now after the update. Previously had all but one diff auto approved, now every diff is auto approved.
Version: 2.5.25 (user setup)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045
The only option is downgrade
I’ve encountered the same issue, and I only noticed it recently.
Version: 2.5.25 (user setup)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100
Same for me.
Not fixed in 2.5.25
Cursor was pushing me to update for 2 weeks, keep saying “You use a very old version of Cursor, update it”. I have updated it yesterday and falled head first into this bug…
I miss my “very old” version of Cursor ![]()
(v2.5.22)
Yay, mine is back to normal now.
Still not recovered

