{"version":"2.1.284","anchor":"file-sync-reflog-replacement-detection-and-windows-unsafe-n","canonical_anchor":"file-sync-reflog-replacement-detection-and-windows-unsafe-n","heading":"Syncing a cloud session's branch to your checkout adds more safety checks","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/file-sync-reflog-replacement-detection-and-windows-unsafe-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Syncing a cloud session's branch to your checkout adds more safety checks\n\nBranch sync from a cloud session now undoes or refuses a branch move if git's records changed underneath it, and rejects unsafe Windows file names\n\n**Unclear.** It is not clear what switches this sync feature on.\n\n**What**\n\nClaude Code can bring a branch from a cloud session into your local git checkout. That step now has more checks:\n\n- Branch history records: git keeps a log of where each branch has pointed. Claude Code saves a copy of these logs first. If one was replaced while the new commits were received, it refuses and the branch is not moved.\n\n- Branch folder changes: if any folder under the checkout's refs\/ folder, where git stores branch names, changed while git moved the branch, the move is undone.\n\n- Windows names: path parts containing <, >, \", |, ?, *, a backslash or control characters are refused as unsafe.\n\n**Why**\n\nThis step writes to your own git branches. The checks stop it from leaving a branch in a wrong state when something else changes the repository at the same time.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}