IssueRaiser

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Software)

[Meta] Feedback on granular control over Copilot changes

justschenOct 2, 2026, 6:59 PM

>[!IMPORTANT] > _October 22 Update:_ Before commenting, please review the latest updates from the team below https://github.com/microsoft/vscode/issues/339363#issuecomment-6346982654 --- As we continue investing in more agentic workflows and improving Copilot, the way changes are made, reviewed, and accepted has evolved. We removed the **Keep** and **Undo** controls for individual changes in chat as part of a shift toward reviewing the overall changes from an agent task, with the intent of simplifying review for longer, multi-file workflows. We recognize that this removed useful checkpoints for incremental, file-by-file review, and that reviewing the overall result does not replace those workflows for everyone. Changes should still be visible and reviewable **per turn, per session, and per branch**. A similar `changes` flow also still exists via the `changes` pill above the chat input. Clicking on this pill opens up the diff editor, which allows you to revert certain lines or edits. This issue is a central place to collect feedback on **granular control over Copilot changes, keep and undo**. We’d like to understand when and how you review changes, whether you can easily inspect them at the scope you need, and where you need more control over accepting or reverting them. Would love to hear more about where the current experience creates friction, including any workarounds, and that will help inform future improvements to the change-review experience! Thanks! --- *

Comments (0)

No comments yet. Start the discussion.

Comment on this issue