{"version":"2.1.302","anchor":"remote-session-bootstrap-failures-handled-more-precisely","canonical_anchor":"remote-session-bootstrap-failures-handled-more-precisely","heading":"Clearer message when a cloud session fails to start","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/remote-session-bootstrap-failures-handled-more-precisely","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Clearer message when a cloud session fails to start\n\nIf a cloud session never starts, Claude Code now says so and asks you to resend your messages, instead of blaming a disconnect\n\n**Unclear.** When the new computer-folder option appears in the permission prompt, and what choosing it does, is not stated.\n\n**What**\n\nA cloud session runs Claude Code on Anthropic's machines instead of your own. When such a session fails to start, Claude Code now:\n\n- reports the failed start as a failed step\n\n- drops the messages waiting to be sent and tells you the cloud session didn't start, so you should send them again\n\n- leaves out the success line if any step failed\n\nBefore, it always said the session had disconnected before its container, the isolated computer it runs in, was ready.\n\nSeparately, when a check about folders on your computer is on, the permission prompt now gets an option for allowing such a folder and is marked as a computer-folder prompt.\n\n**Why**\n\nIf the cloud session never started, you now get an accurate message and know to resend, instead of a misleading one about a disconnect.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}