"Keep All" & "Undo All" unexpected swap

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

“Keep All” & “Undo All” will swap positions when the “changed files” is expanded or not.

Steps to Reproduce

Let agent edit files, scroll chat history up and down.

Expected Behavior

Will not swap position.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.17 (user setup)
VSCode Version: 1.105.1
Commit: 6757269838ae9ac4caaa2be13f396fdfbcf1f9a0
Date: 2025-11-21T08:55:17.983Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report. This looks like a UI consistency bug in the agent review panel.

From your screenshot, it seems the button order changes depending on whether the “changed files” section is expanded. That definitely shouldn’t happen.

I’ll pass this on to the team for further investigation. As a temporary workaround, you can still use the buttons, just be careful which one you click when the layout shifts.

If you notice any other patterns for when this happens, please let me know.

You are absolutely right!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When reviewing changes in the “Files Changed” panel, the button positions for Undo All, Keep All, and Review are inconsistent between expanded and collapsed states.

Collapsed: Keep All is on the left, Undo All on the right

Expanded: Undo All becomes the left-most button, and Keep All moves to the right

This inversion causes frequent accidental clicks on Undo All, especially when reviewing multiple files.

Steps to Reproduce

Open the “Files Changed” panel with several modified files.

Make sure the panel is tall enough so that scrolling is possible.

Scroll to the top, where only the panel header (e.g., “9 Files”) is visible.

Observe the button order: Keep All is on the left, Undo All is on the right.

Now scroll down until the list of modified files becomes visible inside the panel.

Once the file list is visible, the button order suddenly changes:

Undo All jumps to the far left

Keep All moves to the right

Scroll up/down again — the button order flips back and forth based on scroll position.

This inconsistent behavior makes it very easy to accidentally click Undo All, which discards all changes without confirmation.

Expected Behavior

The action buttons (Undo All, Keep All, Review) should keep a consistent layout and position regardless of scroll position within the “Files Changed” panel.

Scrolling the panel—whether only the header is visible or the modified files are visible—should not cause the button ordering to change. Users expect stable button placement, especially for destructive actions like Undo All.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

[Window Title]
Cursor

[Main Instruction]
Cursor

[Content]

Version: 2.1.26 (system setup)
VSCode Version: 1.105.1
Commit: f628a4761be40b8869ca61a6189cafd14756dff0
Date: 2025-11-24T05:39:06.655Z (4 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Them switching sides is the most frustrating behavior…

I can’t undo the decision or reapply the prompt, I’m wasting actual dollars thanks to my usage each time, and it’s happening daily.. I’m burnt out on these intentional bugs, it swaps for me when a new file is created, if I’m accepting all the changes by clicking keep all, it’ll change. In my case it’s just bad UI from constantly changing things.
Devs need things to be stable we’re fragile.
Why do we not have an option to reapply for free when the data is already local?
Now I have to pay to roll the dice again? Devs want more control not less :frowning:

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