Feature Request: Option to disable auto “Jump to next edit” after approving a Copilot/AI edit

[willmruzek]

Feature Request: Option to disable auto “Jump to next edit” after approving a Copilot/AI edit

Summary

When reviewing Copilot/AI-generated edits (e.g., inline edits / next edit suggestions / agent edits), VS Code automatically moves focus (or scrolls/jumps) to the next edit after I approve/keep the current edit. I want an option to disable this automatic jump, so that approving an edit only applies it and leaves my cursor/viewport where it is.

Why this is needed

Auto-jumping is disruptive in review workflows where I want to:

• re-read the surrounding context after applying the change
• make a small manual adjustment near the applied edit
• decide when to move to the next edit (keyboard-driven review)
• avoid losing my place in the file when multiple edits exist

Proposed behavior

Add a setting to control what happens after approving/keeping an AI edit, for example:

• Default (current): after approval, automatically jump to the next edit
• New option: after approval, do not jump; keep cursor/scroll position unchanged
• (Optional future extension, but not required for this request): allow choosing among:
  • stay
  • jump to next edit in same file
  • jump to next edit in workspace

Additional notes

• Searched: https://github.com/microsoft/vscode/issues?q=is%3Aissue+%22next+edit%22+OR+%22jump+to+next+edit%22
• If there is an existing setting/command to control this, I couldn’t find it. I looked for settings related to “next edit”, “jump”, “approve”, “keep”, “inline edits”, but didn’t find a toggle for post-approval navigation.

[zhuamber370]

Support this request. In review-heavy flows, auto-jump after approve breaks local context and slows down precise edits.

A low-risk design could be:

• setting: chat.agentEdits.postApproveNavigation = next | stay
• command pair: Approve and Stay vs Approve and Next
• preserve cursor+viewport anchor when stay is selected

This keeps current default behavior while enabling keyboard-driven review loops.

Would a per-workspace override make sense here (teams often differ on review style)?

[jrieken]

To verify

Verify default behavior (setting enabled):

1. Open a workspace and start a chat editing session that produces changes across multiple files
2. Open the diff editor for one of the modified files
3. Click Keep (file-level) → editor should auto-jump to the next changed file
4. Undo the keep, then click Undo (file-level) → editor should auto-jump to the next changed file
5. For hunk-level: accept/reject individual hunks until none remain in the file → editor should auto-jump to the next changed file

Verify disabled behavior:

1. Open Settings and set chat.editing.revealNextChangeOnResolve to false
2. Start a new chat editing session with changes across multiple files
3. Open the diff editor for one of the modified files
4. Click Keep (file-level) → editor should stay on the current file, no auto-jump
5. Undo the keep, then click Undo (file-level) → editor should stay on the current file
6. For hunk-level: accept/reject all hunks until none remain → editor should stay on the current file, no auto-jump to the next file

Verify setting registration:

1. Open Settings UI and search for revealNextChangeOnResolve
2. Setting should appear under "Chat > Editing" with a checkbox, default checked

[willmruzek]

@jrieken Yes!

It would be nice to have a 'Go to next (file)' button too.

Basically, manual nav.

[willmruzek]

Basically, manual nav.

Oh, never mind. We have that already. 😅