{"version":"2.1.269","anchor":"bash-tools-allowed-domains-validation-moved-into-validatein","canonical_anchor":"bash-tools-allowed-domains-validation-moved-into-validatein","heading":"Bash tool's allowed_domains validation moved into validateInput","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/bash-tools-allowed-domains-validation-moved-into-validatein","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Bash tool's allowed_domains validation moved into validateInput\n\nBash tool now checks allowed_domains sandbox compatibility earlier, during input validation\n\n**What**\n\nThe `Bash` tool's check that `allowed_domains` (a setting that restricts network access to specific domains) only applies to commands running in the sandbox now also runs during input validation, before permission checks happen, in addition to the existing check that runs at permission-check time.\n\n**Why**\n\nThis surfaces the same sandbox-compatibility restriction earlier in the command-handling flow, which can catch invalid `allowed_domains` usage sooner.\n\n- Area: Bash Tool\n- Names: `allowed_domains`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}