Sync conflicts save the incoming file as a dated "conflicted copy" and leave yours alone.
What's wrong with this entry?
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.
- 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.
Claude's conflicted copy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.