{"version":"2.1.310","anchor":"sandbox-failure-message-strips-a-new-prefix","canonical_anchor":"sandbox-failure-message-strips-a-new-prefix","heading":"Cleaner wording when the sandbox cannot start","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/sandbox-failure-message-strips-a-new-prefix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Cleaner wording when the sandbox cannot start\n\nThe 'Sandbox cannot run' message now drops a leading 'cannot start here:' from its reason, so the explanation reads more cleanly\n\n**What**\n\nThe sandbox is a restricted area Claude Code can run commands in, so they cannot touch more of your computer than they should. When it cannot run, Claude Code shows a message starting with 'Sandbox cannot run:' followed by the reason. That reason already had 'sandbox is enabled but' trimmed from its start. Now a following 'cannot start here: ' is trimmed as well.\n\n**Why**\n\nThe tidier wording points to a new kind of failure, where the sandbox cannot start in the current place, and the message now reads cleanly when that happens.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}