Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Rewind/fork snapshot restore now detects worktree changes since the snapshot was read

Rewind/fork restore now refuses to apply a snapshot if worktree files changed since it was taken

You'll notice Improvements
JSON All of v2.1.280
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What

Rewind and fork let you restore a project's files to an earlier saved snapshot. The restore logic now compares the snapshot's recorded file states against the current state of the working files (the worktree) before applying it. If any tracked file, or its file metadata, changed after the snapshot was taken, the restore is refused with a "not applied" result and reason worktree_changed, instead of applying a now-stale snapshot on top of newer changes.

Why

This prevents rewind or fork from silently overwriting file changes made after a snapshot was captured, which could otherwise cause quiet data loss.

See this entry in the whole of v2.1.280 →

Feedback