{"version":"2.1.265","anchor":"new-per-artifact-sandbox-egress-setting-tracked-with-stalene","canonical_anchor":"new-per-artifact-sandbox-egress-setting-tracked-with-stalene","heading":"New per-artifact sandbox egress setting tracked with staleness","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-per-artifact-sandbox-egress-setting-tracked-with-stalene","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New per-artifact sandbox egress setting tracked with staleness\n\nEach artifact now tracks its own sandbox network-access setting, which goes stale after a time limit\n\n**What**\n\nClaude Code now records, per artifact, whether its sandbox (an isolated execution environment) has network egress (outbound network access) disabled or not. This setting is cached, but after a set age it's treated as unknown rather than trusted, so it must be re-checked.\n\n**Why**\n\nCaching the setting avoids repeatedly re-checking it, while the staleness cutoff makes sure Claude Code doesn't act on a network-access setting that may no longer be accurate.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}