No longer showing diffs for code changes, auto-approving

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor just made some changes and they are not in the diff and I didn’t have to accept them. It is only showing the diffs if it updates or adds an import statement it seems

I was implementing a plan with Opus 4.6 Max

Steps to Reproduce

Create a plan. Click Build. Watch cursor modify your codebase without any diffs. Cool

Expected Behavior

It should show me diffs for me to accept.

Operating System

Windows 10/11

Version Information

Version: 2.6.18 (user setup)
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.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?

Opus 4.6

Additional Information

I am really getting tired of bugs shipped with literally every single update of the past month. I am considering alternative tools. Until then, I won’t be updating Cursor anymore (assuming this bug gets fixed, I will update to that)

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes

Hey, this is a known bug that’s been affecting multiple users since around v2.5.24. The team is aware and tracking it.

There’s a workaround that helped some users. Try toggling the Inline Diffs setting:

  1. Go to Cursor Settings > Agents > Inline Diffs
  2. Turn it off, then back on
  3. Restart Cursor

If that doesn’t help, a clean reinstall might be needed. Uninstall Cursor, delete AppData\Roaming\Cursor, then reinstall it fresh. One user in this thread confirmed it fixed the issue for them: How to Enable Diff Review UI After Latest Update?

There’s also a bigger thread tracking this here: Only some diffs are shown whhen agent makes changes

In the meantime, you can use the Review panel in the sidebar and git diff to review changes before committing. It’s not ideal, but it works as a safety net.

Let me know if the toggle workaround helps.

@deanrie The suggested workaround did not work. You all really need to change your approach to updates. You cannot expect users to do full uninstalls and kill all the profile/settings data (which is time-consuming to recreate) whenever you bork existing users with barely-tested updates you push out. This is KILLING my workflows and as much as I love Cursor when it works, I am suggesting we seek alternatives at my company for this sole reason. I have been using Cursor for 1.5 years and for the past year this has been the case with more than half the updates you push out. Very frustrating

3 Likes

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.