{"version":"2.1.283","anchor":"file-sync-new-messages-for-conflicts-at-create-compliance","canonical_anchor":"file-sync-new-messages-for-conflicts-at-create-compliance","heading":"Clearer file sync messages for conflicts, restricted connections and empty starts","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-sync-new-messages-for-conflicts-at-create-compliance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Clearer file sync messages for conflicts, restricted connections and empty starts\n\nCloud file sync now gives specific messages for unresolved git conflicts at session start, restricted connections and empty-start checkouts\n\n**What**\n\nCloud file sync, which copies your working folder to a cloud session, now handles several edge cases differently:\n\n- Unresolved git conflicts when a session is created: the message now says the conflicted files did not go up and will go with your first message once you resolve the conflicts or abort the merge, rebase, cherry-pick, revert or stash pop. Before, this used generic wording.\n\n- A connection lost for compliance reasons: Claude Code no longer re-announces the folder or retries the first upload.\n\n- The install acknowledgement is now skipped while an upload has been announced.\n\n- A file that cannot be read because of where its attributes come from now gets its own suggested fix.\n\n- A checkout started empty, when a synced session is not offered: the message now explains that a synced session would have to start from one upload of the checkout's history and files.\n\n**Why**\n\nThese messages appear directly in unusual situations, so they tell you more precisely what happened and what to do.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}