{"version":"2.1.238","anchor":"claude-cloud-explains-when-your-local-changes-cannot-be-uplo","canonical_anchor":"claude-cloud-explains-when-your-local-changes-cannot-be-uplo","heading":"claude --cloud explains when your local changes cannot be uploaded","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/claude-cloud-explains-when-your-local-changes-cannot-be-uplo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### `claude --cloud` explains when your local changes cannot be uploaded\n\n`claude --cloud` now says why your local changes could not be uploaded and points you at `--ref`.\n\n**What**\n\nStarting a cloud session that cannot ship your working tree now says no session was started and why: either the local changes were too large, or bundling them failed. Both messages point you at `--ref <branch>` to start from GitHub instead, with file sync off.\n\n**Details**\n\n- The two reasons are distinguished internally as `local_changes_too_large` and `local_changes_bundle_failed`.\n\n**Evidence**\n\n`so the working tree cannot be uploaded instead`\n\n- Area: Cloud Sessions\n- Names: `--cloud`, `--ref`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}