Before cursor asked me if i want to approve the changes like each line it edited or made it asked me if i want to keep it or not but now it just edits without asking me i cannot find the option to revert this change. I googled about what setting is causing it but i cannot find it, can someone guide me as to where the option is to turn it off?
Same problem. Version 2.5.20. With this mechanism, the cursor becomes unsafe. Guys, please bring this option back, otherwise I’m canceling my subscription. Not everyone uses GitHub.
I rolled back to version 2.3. It’s working fine. But the situation is unpleasant, and it’s good that it happened outside of work hours, so I noticed it in time. Otherwise, it would have messed things up, of course((
rolle back to 2.3 version only
i even cannot see the differences for some of the cursor windows manipulating md files
how can i do the roll back?
Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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: Darwin arm64 24.6.0
Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
A few days ago, Agent mode was working as expected. When the Agent generated file changes (editing existing files or creating new ones), it showed a review interface at the bottom of the screen that allowed me to accept or reject changes before they were finalized.
After the recent update, this behavior changed.
Now, when using Agent mode:
1- The Agent directly applies file changes automatically.
2- No review interface appears.
3- There are no Accept / Reject controls.
4- The changes are immediately finalized without user confirmation.
This removes user control over file modifications and makes it risky to use Agent mode in active projects.
Steps to Reproduce
- Open any existing project.
- Make sure Agent Mode is selected.
- Ask the Agent to modify an existing file or create a new file.
- Wait for the Agent to complete the task.
- Observe that the changes are immediately applied to the files.
- No review interface (Keep/Undo controls) appears.
Expected Behavior
After Agent generates file changes, a review interface should appear at the bottom of the screen allowing the user to:
- Accept changes file-by-file
- Reject changes file-by-file
- Keep All
- Undo
Changes should not be finalized without explicit user approval.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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.26200
For AI issues: which model did you use?
Auto
Additional Information
This behavior started immediately after updating Cursor to the latest version.
Previously, Agent mode required user approval before finalizing file changes. The workflow was safe and controllable.
Now changes are automatically applied and accepted without any review interface appearing.
This significantly impacts workflow safety when working on production or active projects.
Videos attached demonstrate the issue clearly.
Does this stop you from using Cursor
Yes - Cursor is unusable
The same problem happens after update to 2.5.17
Reverting to 2.4 fixed everything for me. Cursor · Download
Make sure this setting is set after reverting:
Cursor auto updated me to 2.5.20 after I rebooted. I had reverted to 2.4 and it was working fine all yesterday. New day, boot up, same problem, and I check the version and its 2.5.20. I never agreed to install the latest update.
For the record, this setting makes no difference to the issue of showing diffs:
Update:
Setting this to manual stopped the auto updating after downgrading.
Since Cursor is hiding my posts now. Let me rewrite it and try not to appear annoyed.
Cursor auto updated me to 2.5.20 after I rebooted. I had reverted to 2.4 and it was working fine all yesterday. New day, boot up, same problem, and I check the version and its 2.5.20. I never agreed to install the latest update.
For the record, this setting makes no difference to the issue:
Time to reinstall Cursor again…
Update: nevermind this is a new bug that auto installs the latest version. Am I missing some setting somewhere that enables this behavior?
This setting doesn’t show a notification for some reason:
Yea, it sucks. We’ve been reporting and pleading for a fix for 3-4 days now. It’s ridiculous.
Cursor is also hiding this comment of mine despite having positive reactions from the community. I was asking about the workflow of the Cursor team, and how such a bug wasn’t caught in automated tests. I have no issue with arbitrary moderation in private communities of devs who give their time for free. When you join such a place, you are entitled to positivity. This is different, we are paying customers with concerns. There is no better place to express honest user sentiment.
The latest updates have introduced a number of serious issues that are disrupting the normal workflow of many developers. We pay for Cursor and rely on it to earn a living. Naturally, we are angry and frustrated by this. However, instead of explaining why these issues occurred and fixing them promptly, the Cursor team has chosen to hide negative comments. This behavior is both disappointing and alarming, and it reveals their true attitude towards the developer community.
Hey there!
We have forum guidelines, and we just ask that feedback stays constructive. You can find plenty of critical feedback on the forums, and we think that’s healthy and drives us to make a better product.
When something crosses a line, we ask authors to edit their post (which automatically makes the post visible again). In rare cases, we may temporarily pause posting privileges to let things cool off. We do this to keep the community healthy.
A fix is coming, and we do sincerely apologize for the disruption. We understand the urgency surrounding this, and we are making progress.
Version: 2.5.20 (system setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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.26200
Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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: Darwin arm64 22.6.0
I tried manually installing a back version of the app. This gave me the inline diff view again briefly, but then the app seemed to auto upgrade to v 2.5.20 again and I lost the visibility.
Can you consider redacting the latest release to give us a stable working version until you have the bug resolved?
I am also experiencing the ‘auto update’ behaviour reported by other users, after installing previous versions that don’t have the ‘diffs not showing’ bug.
Eg, install 2.4, diffs are showing again as expected, close Cursor at the end of the day, re-open Cursor the next day and Cursor has automatically been updated to the 2.5 version which has the bug (which then requires that I re-install the 2.4 version again).
Same issue with 2.5.20 not showing all the diffs.
@Colin Something I would really like to see with Cursor is either slower more tested updates or a willingness to roll back breaking changes. Cursor is great but having it be often unusable for days at a time has me looking for alternatives.
Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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