Changes getting applied without asking, existing files getting deleted when undoing changes

[Jean-Marie_Dalmasso]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve been running into these problems over and over again and they are becoming a serious problem in my work:

1. Undoing all changes in an existing file (by clicking in top right corner) sometimes just deletes the whole file. That can’t be undone, i have to ask AI to recreate it from memory.
2. Sometimes the changes are applied immediately to files without me even being able to confirm them.
3. Undo All in the chat after stoping on ongoing chat, applied all the changes anyways!!!

It’s becoming so difficult to work with because of these issues potentially messing up dozens of files that then have to be undone manually.

Every release lately has been making the IDE worse. I’m not talking about the AI, which is great, but these other issues are HUGE problems and I don’t understand how they are getting through and not being fixed. They completely break my workflow and make me seriously consider a different editor.

Steps to Reproduce

1. have the ai suggest changes and then decide you don’t want all the changes in one file and POOF the file just gets deleted.
2. Reviewing changes made to a file by the agent only asks for confirmation for the imports and then everything else was auto applied
3. Stop the chat after it’s made a bunch of edits, and then click Undo All, and nothing gets undone, everything is applied, no confirmation is shown.

Operating System

MacOS

Version Information

2.5.17 but has been getting worse and worse over the last 2-3 versions

For AI issues: which model did you use?

I use Auto all the time

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[nedcodes (Ned Cole)]

i hit the same file deletion thing a while back. if you undo a diff on a file the agent created (not one that already existed), it reverts by deleting the file entirely because from cursor’s perspective the “original state” was no file at all.

for existing files getting auto-applied though that’s new to me. are you on 2.5.17 stable or early access?

[Jean-Marie_Dalmasso]

Yes on 2.5.17

Version: 2.5.17 (Universal)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

[deanrie]

Hey, thanks for the detailed report. We’re aware of all three issues, so I’ll go through them one by one:

1. Undo deletes the whole file
   This is one of the most common complaints right now. One important detail: if the file was created by the agent in the current session, Undo treats the “original state” as the file not existing, so it deletes it. This behavior for newly created files should be fixed in the next update. But if this happens to files that existed before you started the agent, that’s a different bug. Can you clarify which case you’re seeing?

2. Changes are applied without confirmation
   There’s an active thread about this with 33 likes: Only some diffs are shown when agent makes changes. The team is aware and looking into it.

3. “Undo All” applies changes instead of undoing
   This is tracked too. It’s really inconvenient, especially when many files are involved.

As a workaround for now, before big agent sessions, make a git commit so you can always roll back with git checkout if something goes wrong.

I shared your report with the team, it helps with prioritization.

[Jean-Marie_Dalmasso]

Great thank you for the fast response and good to know the team is on it.

1. I tend to have a very long session running so most likely it’s the same bug.

I’ll follow your tips for the other issues. Thanks!