Undo All in multi-file edits is too easy to trigger and has no confirmation

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When applying AI changes across multiple files, the UI shows Undo All and Keep All next to each other. It is very easy to accidentally click Undo All, especially when quickly reviewing and applying edits.

There is no confirmation dialog, and the action immediately discards all pending changes.
I have already accidentally lost part of my code this way after misclicking Undo All.

Please consider adding one of the following:

  • a confirmation dialog before executing Undo All (or make a checkbox in settings to use confirmation for this button)
  • an option to require confirmation for destructive actions
  • moving Undo All away from Keep All to reduce accidental clicks

Steps to Reproduce

Any changes by a model.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
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: Linux x64 6.17.0-14-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known pain point. A few users have reported accidental clicks on “Undo All” that caused them to lose work. See this thread for example: I just mistakenly clicked the UNDO ALL button and all my files and code are gone

For now, here are a couple tips to reduce the damage if it happens again:

  1. Git is your safety net. If the files were committed before the agent changes, git restore . will bring everything back.
  2. Checkpoints in the chat sidebar let you roll back to the agent’s last checkpoint.
  3. Local History/Timeline. Right-click the file in Explorer and check the Timeline for snapshots.

Let me know if any of these steps helped.

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