{"version":"2.1.269","anchor":"network-egress-sandbox-classifier-gating-simplified","canonical_anchor":"network-egress-sandbox-classifier-gating-simplified","heading":"Network-egress sandbox classifier gating simplified","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/network-egress-sandbox-classifier-gating-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Network-egress sandbox classifier gating simplified\n\nSandbox network classifier's internal enable-check was simplified from several conditions to two\n\n**Unclear.** Whether this changes which sessions actually get the network classifier applied, or is purely an internal refactor, is not stated.\n\n**What**\n\nThe internal logic that decides whether Claude Code's sandbox network-egress classifier (the mechanism that restricts which network destinations a sandboxed process can reach) applies was reduced from checking several separate conditions down to two. A related mode check used at multiple call sites was also renamed as part of this cleanup.\n\n**Why**\n\nThis is an internal simplification of how the sandbox decides when to apply network classification; it should make that decision path easier to follow, though the finding doesn't indicate any change in which sessions actually get sandboxed network restrictions.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}