Keep/Undo change feature now hops ahead, often way too far

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Keep/Undo change button, shown in code files changed by the agent, was relateively recently changed to auto-hop ahead. At first this seemed ok, but the more I use it, the more I realize the feature is broken, and it yanks me forward, often even to the next code file, before I am really done reviewing the changes AND THEIR CONTEXT.

It is not uncommon for me to initially accept or undo a change, then decide I wanted to review it more fully and do CTRL+Z to undo and re-review. However, with the new behavior of this feature that is CONSTANTLY PUSHING you or YANKING you to the next change, reviewing changes the way I prefer has become much more challenging and frustrating.

A key issue here is that, as you move through changes, the auto-forwarding “marker” for the “next” change that you should be pulled to, moves forward and never moves backward. So if you accept or undo a change, then CTRL+Z to undo your selection to review in more detail, especially if you undo several, the moment you act on one of those restored changes, you are again YANKED forward to wherever the marker ended up before you undid your selections.

Sometimes, it is after reviewing later changes, that my understanding of earlier changes becomes clearer and my original choice to keep or undo is determined incorrect. I try to move quickly, but, the ability to CTRL+Z my actions is AWESOME, because if I act on changes before I necessarily fully understand the whole context of all changes, I can go back and update my choices.

The whole automatic forwarding you through changes has proven to be extremely counter-productive to the way I actually review code changes by the agent. It seems like another one of those “nanny” features, where the agent is trying to help you or save you from yourself, much like sandbox terminals, when in fact, I have no interest in the IDE helping me or saving me in these ways. I want to be in total control here, and it turns out this new behavior by the IDE is actually UNHELPFUL and causes its own problems.

Steps to Reproduce

Choose keep or undo on a change.
Repeat for a few changes.
[Moved forward to next change, even next file.]
Use CTRL+Z to undo your last few actions on the previous changes.
Chose a different action on the change.
[YANKED forward to the change you were last yanked to, skipping all other intervening changes that still need re-review.]

Expected Behavior

I’d prefer an option to disable the automatic behavior of accepting/undoing a change, so I can be in total control myself at all times, and not have the ide forcing me forward, onward, ever to the next thing, when I am not ready to move on myself.

When the option is set to automatically move forward, then the “next” change marker should account for the user using CTRL+Z to undo their selections on previous changes, so that once another action is performed, they aren’t unduly yanked too far ahead to a change well beyond the current changed being reviewed.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
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.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for the feedback, I’ve passed it on to the team.

1 Like

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