5 ms·

No, that's not the point of this new checkpoints feature. It's already been possible for a while to rewind context in Claude Code by pressing <ESC><ESC>. This f

No, that's not the point of this new checkpoints feature. It's already been possible for a while to rewind context in Claude Code by pressing <ESC><ESC>. This feature rewinds code state alongside context: > Our new checkpoint system automatically saves your code state before each change, and you can instantly rewind to previous versions by tapping Esc twice or using the /rewind command. https://www.anthropic.com/news/enabling-claude-code-to-work-more-autonomously https://www.anthropic.com/news/enabling-claude-code-to-work-... Lots of us were doing something like this already with a combination of WIP git commits and rewinding context. This feature just links the two together and eliminates the manual git stuff.

nojs 1y ago
From the docs it looks like this feature only reverts the edit tool calls, and not e.g. bash commands that have been executed: > Checkpoints apply to Claude’s edits and not user edits or bash commands, and we recommend using them in combination with version control
- NiloCK 1y ago
  How could they possibly hope to undo bash commands, whose side effects could be anything, anywhere? Hey Claude... uh... unlaunch those
  - 0x6c6f6c 1y ago
    By tracking changes made by a command, like you might with git.
    - ishouldbework 1y ago
      [dead]
    - vermilingua 1y ago
      And how do you propose they track those changes? Do you want to run your LLM through permanent sudo?
  - nojs 1y ago
    I mean a naive implementation of this would just make regular git commits to a special hidden repo and revert them (ignoring changes outside project root). I always assumed that’s how cursor did it. Presumably they have good reasons not to do this, probably related to not accidentally reverting user edits.
pmarreck 1y ago
Since they recommend still using version control anyway, looks like I will stick to my solution of using a git-colocated jj (jujutsu) SCM which automatically makes label-less (no commit message) commits with every file change to every tracked file (new files are automatically tracked). So you get infinite undo.

nojs 1y ago

From the docs it looks like this feature only reverts the edit tool calls, and not e.g. bash commands that have been executed: > Checkpoints apply to Claude’s edits and not user edits or bash commands, and we recommend using them in combination with version control

NiloCK 1y ago
How could they possibly hope to undo bash commands, whose side effects could be anything, anywhere? Hey Claude... uh... unlaunch those
- 0x6c6f6c 1y ago
  By tracking changes made by a command, like you might with git.
  - ishouldbework 1y ago
    [dead]
  - vermilingua 1y ago
    And how do you propose they track those changes? Do you want to run your LLM through permanent sudo?
- nojs 1y ago
  I mean a naive implementation of this would just make regular git commits to a special hidden repo and revert them (ignoring changes outside project root). I always assumed that’s how cursor did it. Presumably they have good reasons not to do this, probably related to not accidentally reverting user edits.

pmarreck 1y ago

Since they recommend still using version control anyway, looks like I will stick to my solution of using a git-colocated jj (jujutsu) SCM which automatically makes label-less (no commit message) commits with every file change to every tracked file (new files are automatically tracked). So you get infinite undo.