{"version":"2.1.307","anchor":"dangerouslydisablesandbox-override-now-also-converts-ask-res","canonical_anchor":"dangerouslydisablesandbox-override-now-also-converts-ask-res","heading":"More commands get the \"Run outside of the sandbox\" prompt","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/dangerouslydisablesandbox-override-now-also-converts-ask-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### More commands get the \"Run outside of the sandbox\" prompt\n\nWhen Claude asks to run a command outside the sandbox, a command that would have prompted you anyway now shows the \"Run outside of the sandbox\" prompt with its reason\n\n**What**\n\nThe sandbox limits what commands can reach on your machine. Claude can ask to run a command outside it with `dangerouslyDisableSandbox`. Before, that request only changed the prompt you saw for commands that were not already denied or set to ask you. Now a command that would have asked you anyway also shows a \"Run outside of the sandbox\" prompt, and that prompt keeps the original reason for asking.\n\nWhen a command could not be fully analyzed because a reserved word follows an assignment or redirect, the prompt now says so.\n\n**Why**\n\nIt changes which prompt you see when Claude asks to leave the sandbox, and the reason for asking is no longer lost.\n\n- Area: Sandbox\n- Names: `dangerouslyDisableSandbox`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}