Unfortunately, it still doesn’t work for me on version 2.5.25. I even uninstalled Cursor and installed it again from scratch. Guys, do you not understand that we use Cursor solely because of this feature? I’m honestly embarrassed that such a critical function has been unsuccessfully “fixed” for several days now. I’m one step away from canceling my subscription and looking for an alternative, while you keep playing around with vibe coding. It seems like you don’t really understand your own product.
4 Likes
@dmas in Settings, if you search for Inline Diffs, is it On or Off?
I still have this issue on 2.5.25
It auto accepts changes with “Inline Diffs” on or off
The issue persists. Is all the code being written by AI these days? Is that why the bugs are becoming impossible to fix?
I’ve updated it, but the problem is still happening. Is there anything I need to change in the settings separately? This is too critical!!
Version: 2.5.25 (system 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.19044
@sim_hyunseung Install the 2.4 version (Cursor Download Link) and disable auto update for the editor. If you are not using any new feature from 2.5, I imagine that is a form of solving it until Cursor team releases a fix. However, it calls my attention that a bug of this level is still ongoing. People are having issues with their prompts and losing tokens by buckets.
Could you please tell me where I can find the setting to prevent automatic updates of the editor?
There are two settings in the editor you need to modify:
"update.enableWindowsBackgroundUpdates": false,
"update.mode": "none"
Those are located under: File → Preferences → VS Code Settings (or via Command Palette → Open VS Code Settings)
Please fix this for us we cant just be accepting code blindly
When I mustered the courage to update Cursor again, I encountered the same serious problem as before.
Initially, I suspected Cursor was being so radical that the latest version forced users to accept code by default.
It wasn’t until I couldn’t find the code acceptance switch in the settings that I realized it was another bug they’d created.
It’s hard to imagine that the update quality of a paid software is so poor.
The bugs they’ve created are more noticeable than the features themselves.
Luckily, I only paid a monthly fee, not an annual one. The official team should apologize to users and provide compensation.
1 Like
So, is it resolved or not?
Still happening for me on the latest version. any update on this?
Try this: press Ctrl+Shift+P and run ‘Toggle Inline Diffs’. That fixed the issue for me.
This is a problem for me and is causing noticeable quality-control issues, and means I can’t track what Cursor is actually doing to my codebase. Using git diffs on revery request of Cursor is not practical since I can’t commit until I review the work and know it’s done properly, and that can take multiple interactions with Cursor before the code meets requirements.
Hello folks, David Gomes from Cursor here. We made a remote change to all running version of Cursor around 30 minutes ago that we believe resolves this issue.
Can you all please let me know if you can still repro this? Closing and reopening Cursor is required to make sure that this change takes effect.
@Manoochehr @MI_mi This setting disabled auto updates for me.
Doesn’t look like it.
I’ve responded to that user in the other thread, just now, the issue should be fixed on 2.5.25 but only in the last 1 hour and also “Inline Diffs” have to be enabled in the Settings.
I can confirm the issue appears to be resolved in 2.5.25 along with the reverting checkpoint issue.
@bladerunner2020
1 Like