{"version":"2.1.227","anchor":"conflicting-files-are-saved-as-a-dated-conflicted-copy-rathe","canonical_anchor":"conflicting-files-are-saved-as-a-dated-conflicted-copy-rathe","heading":"Conflicting files are saved as a dated \"conflicted copy\" rather than overwritten","tier":"notice","area":"Remote Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/conflicting-files-are-saved-as-a-dated-conflicted-copy-rathe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Conflicting files are saved as a dated \"conflicted copy\" rather than overwritten\n\nSync conflicts save the incoming file as a dated \"conflicted copy\" and leave yours alone.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- If that name is taken it appends a counter, trying up to 100 candidates.\n- 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.\n- If no usable name is found the operation is reported as failed instead of clobbering the local file.\n- Applies only on remote worker sessions, under the same environment gate as the syncer.\n\n**Evidence**\n\n`Claude's conflicted copy`\n\n- Area: Remote Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}