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

Plain-language reasons when an unusual git checkout is refused

You'll notice
Useful3 Signal2
Cloud Sessions

Refused checkouts now name the exact layout problem instead of failing vaguely.

What

Checkouts that upload or sync can now say precisely why they were refused: a broken .git file pointer, an administrative directory in an unexpected place, a back-link that does not point at the working tree, a mismatched common directory, a bad placement, or per-worktree configuration.

Details
  • The back-link case suggests running git worktree repair.
  • Per-worktree configuration (extensions.worktreeConfig or a config.worktree file) is named as not supported by upload yet.
  • Replaces generic failures with a named reason per layout.
Evidence

that uses per-worktree configuration (extensions.worktreeConfig, or a config.worktree file), which this upload does not support yet.

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

See this entry in the whole of v2.1.247 →