Stale AI edits persist across sessions with no way to find or bulk discard them

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When Cursor’s AI makes edits across multiple files, there’s no way to:

  • See a list of all files that have pending AI edits
  • Bulk discard/reject all pending edits across the workspace

The problem: I’ll be on a clean branch, open some random file, and suddenly there’s an unrelated diff from weeks ago that I never accepted or rejected. These stale edits pile up over time and there’s no way to find or clear them all at once.

Steps to Reproduce

  1. Make edits across multiple files using the AI agent/composer
  2. Don’t click “Accept All” - leave the pending edits in the diff view
  3. Commit your actual changes via git (the pending AI edits remain in Cursor’s state)
  4. Switch to another branch or continue working on other things
  5. Days/weeks later, open one of those files - the stale AI edits are still shown even though the underlying file content has changed significantly

Expected Behavior

A command like “Discard All AI Edits in Workspace” to reject all pending changes
Or a panel/list showing all files with pending AI edits so users can navigate to them
Pending AI edits from old sessions should be easy to find and dismiss

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z (1 day ago)
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.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report. This is a known issue with the review workflow, and a few users have reported similar behavior:

The team is working on a fix. For now, the workaround is to manually reject the old diffs in each file.

There’s also a feature request for a centralized review panel where you could see all files with pending changes.

You can try updating to the latest version. Some issues with the review list piling up were fixed. If it still happens after updating, let me know.

still persist on newest version. I could manually reject/accept changes but the problem is that I dont have a place where I can list all the files that have these changes - so I basically would have to go through all the files in my repo (impossible) or just do it everytime I come across a change like that. But when I’m in the middle of coding, then its disruptive as i might have uncomitted changes and would not know which of the accepted/rejected changes should be stashed

1 Like