{"version":"2.1.305","anchor":"remote-control-auto-off-reason-for-a-missing-sandbox","canonical_anchor":"remote-control-auto-off-reason-for-a-missing-sandbox","heading":"Cloud sessions explain sandbox problems and what to do next","tier":"notice","area":"Unattended Serving","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/remote-control-auto-off-reason-for-a-missing-sandbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Cloud sessions explain sandbox problems and what to do next\n\nNew messages tell you when a missing or unusable sandbox affects cloud sessions, with hints pointing to \/sandbox and claude apply-project-settings\n\n**What**\n\nA sandbox is a protected area that limits what commands can touch on your machine. Cloud sessions are sessions run on Anthropic's servers. This release adds wording for when the sandbox gets in the way.\n\n- Unattended mode switched off: a new message (`auto_off.reason.sandbox_off`) is shown for cloud-session commands that would run without asking you when the machine's sandbox is off.\n\n- Reason table: a table maps sandbox reasons such as `sandbox_unavailable` and `sandbox_unconfined` to short words and a next-step hint. The hints point to `\/sandbox` and to running `claude apply-project-settings` in the folder \"so cloud sessions pick it up\". It is paired with the label \"Cloud sessions: asking first\". No code using this table was seen.\n\n**Why**\n\nIf you control Claude Code from another device, you are told why unattended running switched off and what to run to fix it, instead of being left guessing.\n\n- Area: Unattended Serving\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}