{"version":"2.1.290","anchor":"cloud-teleport-clearer-errors-a-no-folder-warning-and-a-l","canonical_anchor":"cloud-teleport-clearer-errors-a-no-folder-warning-and-a-l","heading":"Clearer errors and a missing-folder notice when moving a session to the cloud","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-teleport-clearer-errors-a-no-folder-warning-and-a-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer errors and a missing-folder notice when moving a session to the cloud\n\nCloud session errors give reworded advice, and a notice warns when uncommitted files stay local because the launch folder can't be reached\n\n**Unclear.** What changed in the rules for which files are read into the cloud bundle is not described.\n\n**What**\n\nWhen you send a session to run on Anthropic's cloud machines, Claude Code changes several messages:\n\n- Bundle and upload failures give reworded advice on what to do.\n\n- When creating the cloud session fails, the server's own message may be hidden.\n\n- If the folder Claude Code was started in cannot be reached, a notice says: \"The folder Claude Code was started in cannot be reached, so uncommitted file contents stay on this machine. Restart Claude Code inside the repository to send them.\"\n\n- A session ID that cannot be read now produces a more specific error.\n\n**Why**\n\nThe new notice tells you when your unsaved changes (files not yet committed to git) are not going along with the session, and how to fix it by restarting inside the repository.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}