{"version":"2.1.282","anchor":"sandbox-project-settings-excludedcommands-are-ignored-whe","canonical_anchor":"sandbox-project-settings-excludedcommands-are-ignored-whe","heading":"Sandbox excludedCommands only come from trusted settings when unsandboxed commands are forbidden","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/sandbox-project-settings-excludedcommands-are-ignored-whe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Sandbox excludedCommands only come from trusted settings when unsandboxed commands are forbidden\n\nUnder a strict sandbox policy, project settings can no longer exclude commands from the sandbox, and adding an exclusion goes to user settings or is refused\n\n**Unclear.** The debug message lists user settings as trusted too, but it is not confirmed that user settings entries are kept.\n\n**What**\n\n`sandbox.excludedCommands` lists commands Claude Code may run outside the sandbox (the restricted environment that limits what commands can touch). When unsandboxed commands are forbidden, this list is now read only from trusted settings.\n\n- The rule applies when managed settings or a `--settings` file set `allowUnsandboxedCommands: false`, when `forbidUnsandboxedCommands` applies, or when managed settings set `network.allowManagedDomainsOnly`.\n\n- Entries are then read only from managed settings, `--settings` and user settings. Entries in project `.claude\/settings.json` and `.claude\/settings.local.json` are dropped, and a debug line once per session says how many were ignored. The setting's description now states this.\n\n- Adding an exclusion under that policy writes it to user settings instead of local settings.\n\n- If user settings are turned off (for example with `--setting-sources`), adding an exclusion is refused with the code `user_settings_disabled` and a \"Can't exclude\" error explaining there is no settings file where it would take effect. Before, it was saved where it had no effect and the command reported success.\n\nThis has no feature switch.\n\n**Why**\n\nBefore, a repository could list commands in its own settings file and run them outside a sandbox the administrator had made mandatory. The add command also stops claiming success for an exclusion that does nothing. If your project relies on `excludedCommands` under such a policy, move those entries to user settings or ask your administrator.\n\n- Area: Sandbox\n- Names: `sandbox.excludedCommands`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}