Last update broke diffing

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

21/11/2025 update broke diffing review

Steps to Reproduce

Just ask for any change and try to review files

Expected Behavior

Before the update you can see the differences between old file and changes made.
Now it’s all yellow

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.19 (system setup)
VSCode Version: 1.105.1
Commit: 39a966b4048ef6b8024b27d4812a50d88de29cc0
Date: 2025-11-21T22:59:02.376Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. Based on your screenshots, the green highlighting is actually working correctly. Both files are marked as “(new)”, which means they’re completely new files:

  • profiles.js: +29 new lines
  • onboard.js: +163 new lines

When a file is entirely new, Cursor shows all lines in green because everything is an addition. There’s no old version to compare against.

This would only be a bug if:

  • You’re editing existing files and see everything in green (instead of red for deletions and green for additions), or
  • These files previously existed and you expected to see diffs

Could you please try this:

  • Open an existing file (not a new one)
  • Make a small change
  • Review the changes in Agent

Do you see proper line‑by‑line red/green diffs, or is everything still fully highlighted in green?

Hello deanrie,
Thanks for replying.

The thing is that those aren’t new files. But I see everything like new so I can’t do diffing.

I downloaded a previous version of Cursor because I could’t work like that.

Previous version works fine with diffing

Version: 2.0.77 (system setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

1 Like

Thanks for the detailed info - I was able to reproduce this issue and I’m passing it to the team to investigate.

In the meantime, staying on v2.0.77 is the right workaround.

1 Like

Thanks to you for looking at it.

Anything you need I’m here

1 Like