Persistent “Review next file” button appears in the IDE and surfaces outdated files for review that are no longer relevant

[Keith_Powell]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Issue: Persistent “Review next file” button appears on IDE load and while using IDE

On IDE load and while using the Cursor IDE, the “Review next file” button is rendering persistently and appears out of place. When clicked, it redirects me to a file it’s prompting me to review; however, I haven’t worked in this file in months, so the prompt seems incorrect and unexpected.

Additionally, I would prefer not to see this button at all, especially given its current behavior.

This issue began occurring within the last day or so.

Steps to Reproduce

Open the Cursor IDE and notice the “Review next file” button immediately.

Expected Behavior

The user shouldn’t see this button unless there is a current file update to review.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.19 (Universal)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z (6 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.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. I see the screenshot with the button, this is a known issue. Stale diffs from old review sessions can get stuck and show the Review next file button even for files that were committed a while ago. A few users have already run into this:

• AI Agent file review list accumulates stale files and doesn't sync with git status
• Outdated Diffs appearing when not editing file (changes were previously committed)

A few workarounds that helped other users:

1. Close any old chats that might have created those reviews. The review state can be tied to them.
2. If the files are already committed, you can safely click Accept All on the stuck diffs. It just clears the stale review state. To be safe, check with git diff after.
3. If that doesn’t help, make a small change in the file and commit it, that often resets the state.

The team is aware of the issue. Let me know if the workarounds don’t help.

[MidnightOak]

Cursor creates phantom unsaved changes on every restart (requires discarding multiple files)

I’d like to report a bug that I’ve been dealing with for about a month. I kept waiting for it to be fixed, but it doesn’t seem like anything is changing. Bug description: Every time I restart Cursor, it shows a list of files as “modified / needs saving”, even though I didn’t change anything. What happens: I work on a project I make changes and commit There are no unsaved files I close Cursor When I open Cursor again, I suddenly get ~10 files marked as changed/unsaved (changes I did not make…