Proposal to simplify keep/undo UX

[pierceboggan]

We often get commentary about how the Keep and Undo experiences in Chat are confusing. Additionally, it takes up UX real estate that would be nice to reclaim.

Instead:

1. Turn on auto-save for changes from Chat.
2. VS Code already has a view for tracking changes - the SCM view. This is the best place to see the overall changes for a given Chat session.
3. If the user wishes to revert to a previous conversation state, the best way to do this is the upcoming checkpoints feature (or they can undo/redo for now).
4. Keep/Undo can be removed.

This vastly simplifies the UX, and leans into the existing ways people already use VS Code.

[DanielRosenwasser]

If the user wishes to revert to a previous conversation state, the best way to do this is the upcoming checkpoints feature

Is it going to be possible to review between each checkpoint as a diff? While I get point 2:

VS Code already has a view for tracking changes - the SCM view. This is the best place to see the overall changes for a given Chat session.

I personally think it would still be helpful to understand "wait, what's different since last time? I forgot to commit/stage changes".

[justschen]

we had an idea of allowing users to compare changes from that point (kind of like today where you can right click a file to see the file snapshot, but maybe an actual diff editor)

i agree that if we have checkpoints, we wouldn't need undo/redo or the "keep" idea.

iirc, it's also a setting rn for agent mode to autosave changes?

[iwangbowen]

Add checkpoint feature