Files can't be deleted if pending changes exist

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If the agent suggests changes to a file that then gets deleted, the file will persist or the hovering “review next” button will force you to review it.

This is very annoying if like the agent creates a file, but then deletes it programmatically, the review UI will force you to recreate the file.

I have a very special use case where this issue is particularly annoying, but the above is probably what most people can relate to.

Steps to Reproduce

Have agent suggest a change, delete the file programmatically, the file will recreate itself or force you to do so with a “review next” button always hovering.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This looks like a known issue with the review state. Please try the workaround from this solution: "Review next file" button persists on .svg file

  • In the agent chat history, click Review on recent chats
  • For any files showing review controls in the editor, explicitly click Keep All or Undo All
  • Repeat for all affected files
  • Restart Cursor

If the issue persists after programmatically deleting a file:

  • send exact reproduction steps and a short video or screenshots
  • errors from Help → Toggle Developer Tools → Console

I’ll escalate to the engineers with this data.

Oh, no I realized what the issue is more specifically. If an agent edits a currently existing file, then the file is deleted programmatically, regardless of whether I accept or deny the edit, the file is recreated.

In either case (agent created a file or is editing an existing), if the file gets deleted programmatically after, I shouldn’t be asked to review any changes from it regardless.

You can test this with this:

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.