[maxloh]

> What if the agent makes the wrong choice? How many tokens have been burned in the meantime?

It is much worse than that. Claude Code doesn't auto-commit when stopping for an answer. There might be possible data loss if an uncommitted file is edited.

Good luck recovering the file from the JSONL conversation history.

[hombre_fatal]

On the other hand, relying on Claude Code's internal version control puts you at the same mercy of their product decisions and move-fast breakage.

Instead, start with a plan file and tell the agent to break it up into logical commits.

Though I think the bigger issue here is when you're yoloing something mutable, like managing a remote server or driving a browser or troubleshooting your local OS where there's no going back.

[wgd]

It's actually pretty straightforward to recover file-states from conversation history. I accidentally deleted the wrong repo on my machine once and recreated all the lost work from agent chat history. It is, ironically, the sort of task which AI agents excel at.