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.227 Home All releases olderv2.1.226 v2.1.228newer
Claude Code v2.1.227

Conflicting files are saved as a dated "conflicted copy" rather than overwritten

You'll notice
Useful3 Signal2
Remote Sync

Sync conflicts save the incoming file as a dated "conflicted copy" and leave yours alone.

What

When a file arriving from the other side differs from one you changed locally, the sync writes the incoming content to a sibling file named with "Claude's conflicted copy" plus a YYYY-MM-DD date, leaving your version untouched.

Details
  • If that name is taken it appends a counter, trying up to 100 candidates.
  • The base name is truncated so the final file name stays within 255 minus 32 bytes, and candidates that are invalid on Windows are rejected.
  • If no usable name is found the operation is reported as failed instead of clobbering the local file.
  • Applies only on remote worker sessions, under the same environment gate as the syncer.
Evidence

Claude's conflicted copy

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