[Regression] AI edits applying automatically without Diff/Approval UI

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After recent updates, the editor has stopped showing the “Accept/Reject” diff view for AI-generated changes. Instead of showing the inline review UI, the agent applies changes directly to the files. This makes it impossible to partially accept or verify changes before they are finalized.

Steps to Reproduce

Open a project in Cursor.
Open Composer (Cmd/Ctrl + I) or use Agent Mode.
Provide a prompt to edit an existing file (e.g., “Refactor this function”).
Observe that the changes are applied immediately to the file without the standard diff overlay or the “Accept/Reject” buttons appearing.

Expected Behavior

Cursor should show the inline diff view with “Accept” and “Reject” buttons for all file modifications, allowing for manual review before the code is committed to the file.

Operating System

Windows 10/11
MacOS
Linux

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z (4 days ago)
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 25.2.0

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hey, this is a known issue and the team is aware. The main thread is here: Only some diffs are shown whhen agent makes changes

Try this workaround: go to Cursor Settings > Agents > Inline Diffs, turn it off and back on, then restart Cursor. This helps many users get the diff UI back.

For now, you can review changes in the Review panel or with git diff.

Let me know if the toggle helped.

6

The main thread you linked is locked. @mohitjain

7

Have rectified, thanks for letting me know.

8

Thanks for sharing, this workaround worked for me.

1 Like
10

Hey @Sohail_Habib!

The regression where AI edits were applying automatically without the Diff/Approval UI has been fixed in a recent Cursor update. Updating to the latest version should resolve this. If you’re still experiencing this on the latest version of Cursor, please raise a new thread and we’ll take a look.