{"version":"2.1.281","anchor":"cloud-session-bundle-upload-failure-now-explains-why-and-how","canonical_anchor":"cloud-session-bundle-upload-failure-now-explains-why-and-how","heading":"Cloud session bundle-upload failure now explains why and how to upload without file sync","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-session-bundle-upload-failure-now-explains-why-and-how","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud session bundle-upload failure now explains why and how to upload without file sync\n\nCloud sessions now say why the local upload failed and how to start with `CLAUDE_CODE_DIR_SYNC_ENGINE=none` instead\n\n**What**\n\nA cloud session runs Claude Code on a remote machine, started with `--cloud`. When Claude Code cannot upload your local folder and the session falls back to starting from the tip of the branch on its remote copy, the message now includes the reason the upload failed.\n\nNew wording also covers these cases:\n\n- Upload failed: explains that you can start without syncing files by running `CLAUDE_CODE_DIR_SYNC_ENGINE=none claude --cloud`.\n\n- Tracked changes only: adds that untracked files stay on your machine.\n\n- Commits only: adds that uncommitted file contents stay on your machine.\n\n- Unsupported host: a message for a remote on a code-hosting service that cloud sessions can't clone from yet.\n\n- Folder too large: the refusal now suggests running with `CLAUDE_CODE_DIR_SYNC_ENGINE=none`, or deleting `remoteFileMode` from the folder's project entry to be asked about syncing again.\n\n**Why**\n\nWhen your local files do not reach the cloud session, you now learn what went wrong, what was left behind, and what to run to start anyway.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}