Cursor keep asking to keep files

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor keep asking to keep files, I need to manually go through every file and manually select top-right button keep-file. Otherwise it always shows changes from previous work (even many chats ago). When I choose ‘review next file’ (after ‘keep file’) - it jumps to first *.svg file in assets , and it has no changes. Not in cursor or git. But if I go manually to the next cpp file - it shows many changes and asks to keep them

Steps to Reproduce

Just use cursor, make changes via agent tab, use new chats. but stage and commit files in other git application, like Fork. At some point you realize when you open Cursor IDE - there are many-many files with your previous work, and still asks to keep them via ‘keep file’ and it shows those changes in the file. But you already commited them long ago (a week, or yesterday, for example).

Expected Behavior

  1. No questions to keep files when they staged and committed in other git-apps.
  2. Review next file must jump to the next unkeeped file, not just the first available file in tree.

Operating System

Windows 10/11

Version Information

Version: 2.4.37 (user setup)
VSCode Version: 1.105.1
Commit: 7b9c34466f5c119e93c3e654bb80fe9306b6cc70
Date: 2026-02-12T23:15:35.107Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22621

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
3

Hey, thanks for the report. This is a known issue. diffs from Review don’t get cleared if you commit using external Git clients like Fork.

Related threads:

A few workarounds that helped other users:

  1. Close the specific chats where those reviews were created. Sometimes this resets the diffs linked to them.
  2. Go back to the old chat and accept the changes from there.
  3. Copy the whole file content (Ctrl+A, Ctrl+C), then undo until the diffs disappear (Ctrl+Z), then paste it back Ctrl+V. This clears the “stuck” state.

About the issue where “Review next file” jumps to the wrong file, like a .svg with no changes instead of the next unreviewed file, that’s a separate bug. Can you share the Request ID from the chat where it happens? (Chat context menu > Copy Request ID)

The team is aware of the “stuck” review issue. We don’t have an ETA yet, but your report helps with prioritization. Let me know if any of the workarounds helped.

4

I’m not sure if you find smth useful, I already selected manually keep file for every file in repo. But also this issue happens for every new chat, not just in one chat.
e43cd745-da59-4690-ba98-f707efae417b

1 Like
5

I keep having this issue as well.