{"version":"2.1.285","anchor":"sandbox-logs-dropped-repo-level-network-filesystem-and-doma","canonical_anchor":"sandbox-logs-dropped-repo-level-network-filesystem-and-doma","heading":"The sandbox may now ignore network and file permissions a repository grants itself","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sandbox-logs-dropped-repo-level-network-filesystem-and-doma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The sandbox may now ignore network and file permissions a repository grants itself\n\nThe sandbox now tracks one-time notices for ignoring a repository's own network, file and allowed-domain settings\n\n**Unclear.** It is not confirmed that these repository settings are actually dropped, or under which conditions.\n\n**What**\n\nThe sandbox is a restricted environment that limits what commands Claude runs can reach. It now keeps track of whether it has logged a one-time notice for each of three kinds of setting coming from a repository:\n\n- network allowances\n\n- filesystem grants\n\n- allowed domains\n\nThese sit beside an existing notice for ignored excluded commands. This points to the sandbox dropping these repository-supplied settings and noting it once each time.\n\n**Why**\n\nIf you rely on a project's own settings to widen what the sandbox allows, those widenings may no longer apply.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}