Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

Snapshot restore checks file mode, not just content

You'll notice
Useful3 Signal2
Snapshots

Snapshot restore now catches file permission changes, so an executable bit flip isn't missed.

What

When a workspace snapshot holds files at their committed state, it now records each path's file mode alongside its content id and fails the snapshot if either differs from what the commit holds. An executable-bit change can no longer pass as an unchanged file.

Details
  • The check reads git's staged file listing including mode, and the mismatch is reported with the existing wording are not the ones HEAD holds.
  • Not gated; runs as part of the normal snapshot path.
Evidence

are not the ones HEAD holds

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.247 →