{"version":"2.1.299","anchor":"cloud-launch-error-messages-and-git-bundle-advice","canonical_anchor":"cloud-launch-error-messages-and-git-bundle-advice","heading":"Clearer errors and advice when starting cloud sessions","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cloud-launch-error-messages-and-git-bundle-advice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Clearer errors and advice when starting cloud sessions\n\nCloud session launches now give plainer errors for `--tools` on self-hosted environments, missing sign-in and some git failures\n\n**What**\n\nStarting a cloud session (a Claude Code session that runs on remote machines) now gives clearer messages when it fails:\n\n- `--tools` on a self-hosted environment: the message now says \"--tools does not work yet with the self-hosted environment\".\n\n- Launches that need a session attached to this computer now get their own refusal message.\n\n- Missing sign-in: the message says cloud sessions need a claude.ai sign-in and suggests running `claude auth login` (or `\/login` in a local session).\n\n- An empty repository that cannot be bundled up for the session now comes with advice.\n\n- A missing-object failure while saving your uncommitted changes suggests retrying and, if it stops again, running `git fsck` in the checkout.\n\nUsage data now also records whether a self-hosted environment was involved.\n\n**Why**\n\nWhen a remote session will not start, the message now tells you what to do next.\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"}