{"version":"2.1.246","anchor":"a-bash-call-using-dangerouslydisablesandbox-no-longer-blocks","canonical_anchor":"a-bash-call-using-dangerouslydisablesandbox-no-longer-blocks","heading":"A Bash call using dangerouslyDisableSandbox no longer blocks remote execution","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-bash-call-using-dangerouslydisablesandbox-no-longer-blocks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A Bash call using `dangerouslyDisableSandbox` no longer blocks remote execution\n\nA Bash call using dangerouslyDisableSandbox can still run on a remote device instead of being forced local.\n\n**What**\n\nThe check that decides which tool input fields prevent a tool call from running on a remote device now filters `dangerouslyDisableSandbox` out of that list, so its presence alone no longer forces local execution.\n\n**Details**\n\n- The filter is a build-time set containing only that one name plus an empty spread, so further exemptions can be added without changing the surrounding code.\n- In the previous build the same helper returned the refusing-field list unfiltered.\n\n**Evidence**\n\n`dangerouslyDisableSandbox`\n\n- Area: Sandbox\n- Names: `dangerouslyDisableSandbox`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}