Source Intelligence

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.239 Home All releases olderv2.1.238 v2.1.240newer
Claude Code v2.1.239

Cloud session sync says why files could not be written back

You'll notice
Useful3 Signal1
Cloud Sessions

Cloud sync now groups failed file writes by cause and names the paths.

What

The pull summary now splits failures by cause instead of listing them together, naming up to a few paths in each group and noting that sync retries every turn.

Details
  • Three groups: a name that collides with an existing file differing only in letter case, files with credential-like names that are never written locally, and everything else.
  • A separate line covers paths git holds behind a filter such as LFS or git-crypt, which only a commit can carry across.
Evidence

from a file already here only in letter case

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.239 →