Add chat.editing.revealNextChangeOnResolve setting to control auto-jump after keep/undo

[Copilot]

After keeping or undoing a chat edit (file-level or hunk-level), VS Code automatically jumps to the next change. This adds a chat.editing.revealNextChangeOnResolve boolean setting (default true) to let users disable that behavior and stay in place.

• constants.ts: Add RevealNextChangeOnResolve to ChatConfiguration enum
• chat.contribution.ts: Register the setting
• chatEditingEditorActions.ts: Guard openNextOrPreviousChange calls in KeepOrUndoAction and AcceptRejectHunkAction on the new setting

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[jrieken]

@copilot I like. How about a better settings name. Instead of chat.editing.autoNavigation I have something with chat.editing.revalNextChangeOnBla in mind. Just no good idea for bla which can be Keep or Undo. Maybe onKeepUndo but also have an idea please

[Copilot]

@copilot I like. How about a better settings name. Instead of chat.editing.autoNavigation I have something with chat.editing.revalNextChangeOnBla in mind. Just no good idea for bla which can be Keep...

Renamed to chat.editing.revealNextChangeOnResolve — "resolve" covers both Keep and Undo since both actions resolve a change. Done in 7846f89.

[jrieken]

@copilot Generate me copy paste friendly steps to verify for this change

[Copilot]

@copilot Generate me copy paste friendly steps to verify for this change

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