{"version":"2.1.283","anchor":"new-specific-reasons-shown-when-cloud-file-sync-is-off","canonical_anchor":"new-specific-reasons-shown-when-cloud-file-sync-is-off","heading":"Cloud sessions now say why file sync is off","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-specific-reasons-shown-when-cloud-file-sync-is-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sessions now say why file sync is off\n\nWhen file sync cannot start for a cloud session, Claude Code now names the reason, such as a network drive or an unsupported platform\n\n**What**\n\nWhen file sync (copying your local files to and from a cloud session) cannot start, Claude Code now shows \"File sync is off for this session:\" followed by a reason. The reasons include:\n\n- a missing native component sync depends on\n\n- the project is on a network drive, with a note that a copy on a local drive syncs both ways\n\n- file identities that do not stay stable\n\n- no \/proc on the system\n\n- a macOS system lacking a safeguard sync needs\n\n- sync failing to start up\n\n- an unsupported platform\n\nIt also says what that means for you, for example that the session starts with no files from this folder, or that it starts from GitHub's copy of the branch or a one-time upload of this checkout.\n\n**Why**\n\nIf you start a cloud session from a local folder and sync does not work, you now get a reason you can act on.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}