{"version":"2.1.219","anchor":"new-sandbox-setting-network-strictallowlist","canonical_anchor":"new-sandbox-setting-network-strictallowlist","heading":"New sandbox setting: network.strictAllowlist","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/new-sandbox-setting-network-strictallowlist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### New sandbox setting: network.strictAllowlist\n\nSet strictAllowlist to have the sandbox flat-out deny hosts outside your allowed domains instead of prompting.\n\n**What**\n\nA `strictAllowlist` boolean on sandbox network settings makes the sandbox runtime deny hosts outside `allowedDomains` outright instead of prompting. The runtime check existed before but there was no way to turn it on.\n\n**Details**\n\n- Added to the sandbox network settings schema and propagated through settings merging (`if (o.strictAllowlist === !0) l.strictAllowlist = !0;`), derived from any of user, managed or CLI settings\n- The runtime permission check is `if (!r || Hl.network.strictAllowlist)`; a host matching no rule is denied rather than prompted when this is on\n- Honoured only from user, managed\/policy or `--settings` sources; per its own description project settings (`.claude\/settings.json` and `.claude\/settings.local.json`) are ignored\n- Described as \"Enforced for sandboxed commands only\"; in-process tools such as WebFetch are not gated by it\n- Absent by default, so behaviour is unchanged unless configured\n\n**Usage**\n\n`{\"sandbox\":{\"network\":{\"allowedDomains\":[\"api.example.com\"],\"strictAllowlist\":true}}}` **Evidence** `the sandbox runtime deterministically denies hosts not in allowedDomains instead of prompting`, `When true, the sandbox runtime deterministically denies hosts not in allowedDomains instead of prompting. `\n\n- Area: Sandbox\n- Names: `sandbox.network.strictAllowlist`, `allowedDomains`, `--settings`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}