Hey, thanks for the detailed report. This is a known bug. The review state doesn’t properly clear after changes are accepted and committed. Several users are running into the same thing:
- AI Agent file review list accumulates stale files and doesn't sync with git status
- Persistent “Review next file” button appears in the IDE and surfaces outdated files for review that are no longer relevant
- Diffs for acceptance become out of sync with committed code when switching branches
The console logs you attached are mostly standard extension warnings and not directly related to this issue.
A few workarounds that have helped others:
- Close the specific chat sessions that originally produced those diffs. The review state is tied to the chat, so closing it can clear the phantom diffs.
- If that doesn’t work, try Accept All on the stuck diffs. Since
git statusis clean, it just clears the stale review state without changing files. You can double-check withgit diffafter to be safe. - As a last resort, try launching with extensions disabled using
cursor --disable-extensionsto rule out extension conflicts.
The team is aware of this. Your report, especially the specific workflow with branch switching after merge, helps with prioritization. Let me know if any of the above helps or if the issue keeps coming back.