{"version":"2.1.311","anchor":"sandbox-install-hint-no-longer-mentions-administrator-run-se","canonical_anchor":"sandbox-install-hint-no-longer-mentions-administrator-run-se","heading":"Sandbox set-up messages now always suggest claude sandbox install","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/sandbox-install-hint-no-longer-mentions-administrator-run-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Sandbox set-up messages now always suggest claude sandbox install\n\nSandbox hints no longer send you to your administrator and always suggest claude sandbox install or \/sandbox install instead\n\n**What**\n\nThe sandbox is a restricted environment Claude Code can run commands in, controlled with `\/sandbox`. When it needs setting up again, Claude Code's messages no longer send you to your administrator:\n\n- The guidance about commands excluded from the sandbox, and the hint shown when sandbox set-up fails, used to say your administrator could run the set-up again. They now suggest running `claude sandbox install` in a terminal, or `\/sandbox install` inside Claude Code. Either way there is one elevation prompt, meaning one request for administrator permission.\n\n- Whether sandbox settings are locked by policy no longer changes which command is suggested.\n\n- After the Windows sandbox is removed, the message now always says to run `claude sandbox install`, or `\/sandbox install` inside Claude Code. The separate message saying set-up was up to your administrator because settings are managed by policy is gone.\n\n**Why**\n\nOn machines where an administrator manages the sandbox, you are now told to set it up yourself rather than to contact them.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}