{"version":"2.1.268","anchor":"commands-carrying-allowed-domains-now-force-an-ask-via-the","canonical_anchor":"commands-carrying-allowed-domains-now-force-an-ask-via-the","heading":"Commands carrying allowed_domains now force an 'ask' via the auto-mode classifier","tier":"notice","area":"Sandbox Network","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/commands-carrying-allowed-domains-now-force-an-ask-via-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Commands carrying allowed_domains now force an 'ask' via the auto-mode classifier\n\nCommands with allowed_domains now always prompt for approval instead of being auto-allowed\n\n**What**\n\nWhen a tool call is restricted to a sandbox network list and carries `allowed_domains` under the relevant sandbox mode, Claude Code's permission check now forces the decision to \"ask\" rather than letting an allow rule or hook approve it silently. The message explains that allow rules and hook approvals cover the command itself but not the specific hosts it's allowed to reach, and that only the auto-mode classifier can approve the `allowed_domains` list.\n\n**Why**\n\nThis closes a gap where a command could be pre-approved without the specific network hosts it's allowed to contact also being vetted, ensuring host access still goes through the classifier meant to review it.\n\n- Area: Sandbox Network\n- Names: `allowed_domains`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}