{"version":"2.1.285","anchor":"sandbox-exposes-trusted-tier-and-configured-grant-getters","canonical_anchor":"sandbox-exposes-trusted-tier-and-configured-grant-getters","heading":"Sandbox can report its configured network and file permissions","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sandbox-exposes-trusted-tier-and-configured-grant-getters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Sandbox can report its configured network and file permissions\n\nThe sandbox can now report its configured network allowances, file permissions and Unix socket setting, and cleans up more after a command\n\n**Unclear.** Whether the check that blocks running outside the sandbox is actually used yet is not clear.\n\n**What**\n\nThe sandbox is the restricted area Claude Code can run commands in, limiting which files and network addresses they can reach. It can now report:\n\n- which network allowances are configured\n\n- which file system permissions are configured\n\n- whether all Unix sockets (a way for programs on one machine to talk to each other) are allowed\n\n- whether a trusted setting has closed off the option of running a command outside the sandbox\n\nThe cleanup that runs after each command now also runs an extra cleanup step.\n\n**Why**\n\nThis suggests stricter handling of sandbox rules, where some configurations can stop commands from falling back to running unsandboxed.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}