{"version":"2.1.299","anchor":"sandbox-command-now-reports-result-of-settings-write","canonical_anchor":"sandbox-command-now-reports-result-of-settings-write","heading":"\/sandbox confirmation now reflects whether the setting was saved","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-command-now-reports-result-of-settings-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### \/sandbox confirmation now reflects whether the setting was saved\n\nAfter you pick a sandbox option in \/sandbox, the confirmation now depends on how saving the setting went\n\n**What**\n\nThe `\/sandbox` command turns sandbox mode on or off. Sandbox mode limits what commands run by Claude Code can reach. After you choose an option, Claude Code prints a confirmation such as \"\u2713 Sandbox enabled with auto-allow for bash commands\". Before, that message was printed every time. Now Claude Code builds the message from the result of saving the setting.\n\n**Why**\n\nThe confirmation no longer has to claim success regardless of what happened when the setting was saved, so it can now point out a problem.\n\n- Area: Sandbox\n- Names: `\/sandbox`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}