{"version":"2.1.304","anchor":"sandbox-reports-unavailable-in-some-sessions","canonical_anchor":"sandbox-reports-unavailable-in-some-sessions","heading":"Sandbox can report itself unavailable in some sessions","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-reports-unavailable-in-some-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sandbox can report itself unavailable in some sessions\n\nIn some sessions Claude Code now reports that the sandbox is enabled but unavailable in this session\n\n**Unclear.** Which sessions this condition applies to is not known.\n\n**What**\n\nThe sandbox is a protected area that limits what commands Claude runs are allowed to touch. In some sessions, Claude Code now stops its sandbox check early and reports \"sandbox is enabled but unavailable in this session\". The same condition also stops the prompt suggesting you install the Chrome extension and stops Claude Code reading sign-in details from standard credential files.\n\n**Why**\n\nIn these sessions the sandbox is turned on in settings but does not protect commands, so it is worth knowing when you see this message.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}