{"version":"2.1.284","anchor":"cloud-session-create-device-binding-is-required-before-a-fo","canonical_anchor":"cloud-session-create-device-binding-is-required-before-a-fo","heading":"Cloud sessions bind your device before syncing a local folder","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/cloud-session-create-device-binding-is-required-before-a-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud sessions bind your device before syncing a local folder\n\nStarting a cloud session that would sync a local folder now binds this device first, and drops the sync with a notice if that fails\n\n**Unclear.** It is not clear which remote switches decide when connected sessions and file sync are used.\n\n**What**\n\nWhen you move work to a cloud session (a Claude Code session that runs on Anthropic's servers instead of your computer), Claude Code can copy a local folder or git checkout up to it. It now binds this computer to your account before the cloud session is created, instead of skipping that step. What happens next depends on the case:\n\n- Device not bound: the folder sync is dropped and you see a notice saying so.\n\n- Linked git worktrees, and checkout layouts that cannot be served, whose branch is already on the remote: the session starts from GitHub instead of trying an upload.\n\n- Attaching to a cloud session: the connection between this computer and the session starts only when the device is bound. Before, it always started.\n\n**Why**\n\nSome cloud sessions now start from the copy of your branch on GitHub, or run without your local files, where they used to upload your local state. If a cloud session is missing uncommitted work, check whether it started from GitHub or whether the sync was dropped.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}