Source Control Highlighting Very Old Changes

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

My source control is keeping highlighting past commits making very difficult to review new changes. Someone had that and know how to fix?

Not happening on VS Code. screenshot comparing atached.

Looks like it highlights not only git diff but what was not explicit accepted on the IDE, even if it was coded without Cursor.

I already tried Git Refresh, reopen folder, nothing. How do i fix this?

Steps to Reproduce

Maybe don’t explicit accept in the cursor the changes but just commit

Expected Behavior

Should show only GIT DIFF when files were clicked

Screenshots / Screen Recordings

Screenshot 2025-12-16 at 3.18.33 AM.png
Screenshot 2025-12-16 at 3.18.33 AM.png434×1352 90.1 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. I see the screenshot with old changes highlighted. Looks like a known bug with “stuck” diff decorations. Here are a few workarounds that helped others:

  • Accept/reject changes via the Git panel, not the inline diff UI
  • Cmd+Shift+P → Developer: Reload Window
  • Run without extensions: cursor --disable-extensions
  • In the problematic file, temporarily delete highlighted blocks, save, then immediately Undo

Similar cases:

Need details to escalate:

  • Request ID of the last operation (in chat: top-right menu → Copy Request ID)
  • 2-3 file paths where highlighting is wrong, and git status output for them
  • Short repro steps and if it happens after Agent Review

Let me know if any workaround helps. If not, gather the info above and I’ll pass it to engineers.

3

I assume this is not fixed because it keeps happening every day on the latest version?