{"version":"2.1.309","anchor":"sandbox-startup-message-and-a-new-refusal-kind","canonical_anchor":"sandbox-startup-message-and-a-new-refusal-kind","heading":"A progress message while the sandbox starts up","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/sandbox-startup-message-and-a-new-refusal-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### A progress message while the sandbox starts up\n\nClaude Code has a new message warning that starting the sandbox and setting file permissions can take a few minutes\n\n**What**\n\nA sandbox is a fenced-off environment that limits what commands Claude Code runs can touch. Claude Code now has a message for when it is starting one: \"Starting the sandbox\u2026 Setting file permissions can take a few minutes.\"\n\nSeparately, when Claude Code sorts out why access to a file path was refused, it now recognises a reason labelled `name_or_place`, alongside the kernel, device and credential reasons it already recognised.\n\n**Why**\n\nA slow sandbox start now comes with an explanation, so a pause at that point is less likely to look like a hang.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}