{"version":"2.1.234","anchor":"cloud-sessions-say-why-your-local-changes-were-left-behind","canonical_anchor":"cloud-sessions-say-why-your-local-changes-were-left-behind","heading":"Cloud sessions say why your local changes were left behind","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/cloud-sessions-say-why-your-local-changes-were-left-behind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Cloud sessions say why your local changes were left behind\n\nStarting a cloud session from a diverged repo now says why it began from GitHub, not your working tree.\n\n**What**\n\nStarting a cloud session from a repo that has diverged from its remote now prints the specific reason the session began from GitHub instead of your working tree, rather than starting silently.\n\n**Details**\n\n- Reasons computed: an operation already in progress, pull not supported, bundling unavailable, repository too large, or an explicit ref was requested.\n- Each reason produces its own sentence, including one stating that file sync is off for that session.\n- Windows gets a separate line saying syncing files back is not supported yet.\n\n**Evidence**\n\n`and bundling is unavailable here, so the session started from GitHub without your local changes and file sync is off.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}