{"version":"2.1.292","anchor":"sandbox-seed-admin-source-and-trusted-source-fallback","canonical_anchor":"sandbox-seed-admin-source-and-trusted-source-fallback","heading":"Sandbox settings gain a new source that can close the unsandboxed fallback","tier":"internal","area":"Sandbox","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/sandbox-seed-admin-source-and-trusted-source-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Sandbox settings gain a new source that can close the unsandboxed fallback\n\nThe sandbox now accepts a `seed-admin` settings source and a new check for whether a trusted source closes the unsandboxed fallback\n\n**Unclear.** It is not stated what the `seed-admin` source is or how you would set it.\n\n**What**\n\nThe sandbox limits what commands run by Claude can reach. Its list of places it takes settings from now includes `seed-admin`. There is also a new check for whether a trusted settings source has closed the unsandboxed fallback, which is the option to run a command outside the sandbox. Previously the check looked only at a trusted level.\n\n**Why**\n\nManaged sandbox policy may now be able to turn off running commands outside the sandbox.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}