Short answer: you can’t truly “rewind” Claude Code the way you’d rewind a git commit or branch a conversation tree inside the same thread. Claude Code conversations are linear logs, not editable DAGs. But you can simulate rewinding very effectively if you treat the conversation like code and manage state explicitly. 🧠🌿

Here’s the mental model that actually works.

Claude Code keeps the entire conversation as context. There’s no native “jump back to message #17 and fork.” Once tokens are in, they’re in. So rewriting later responses doesn’t delete their influence unless you actively override them.

The reliable workaround is to declare a reset point in text, like a soft fork. You do this by telling Claude exactly which assumptions, decisions, or artifacts should now be considered canonical, and which should be ignored.

For example, you write something like:
“Reset context to before we decided on X. Treat everything after that point as discarded. New direction follows.”

Claude is good at honoring explicit instructions like this, especially when you’re precise about what state should survive and what shouldn’t. You’re not erasing history, you’re overwriting the present.

For more complex projects, the power move is to externalize state. Keep a running “source of truth” file in your repo or notes, something like SPEC.md or STATE.md. When you want to rewind, you paste in the earlier version of that file and say:
“This is the authoritative state. Ignore any later divergence.”

Now Claude is anchored to an object, not a conversation haze. This feels much closer to branching.

Another trick that works surprisingly well is checkpointing. Periodically say:
“Checkpoint: this is the current agreed design/plan.”
Later, when you want to fork:
“Rewind to the last checkpoint and explore an alternative branch.”

Again, it’s linguistic control, not UI control, but it’s effective.

If you want a true tree with parallel branches, the only real solution today is multiple threads. One thread per branch. It’s inelegant, but it mirrors how we already work with drafts: duplicate, diverge, compare.

So the meta-lesson is very on brand for Claude Code: treat conversation like mutable code, not sacred history. State beats chat. Explicit beats implicit. And a well-named checkpoint saves more time than any rewind button ever could. 🚀