{"version":"2.1.305","anchor":"device-tool-refusal-text-adds-sandboxallownestedusernamespa","canonical_anchor":"device-tool-refusal-text-adds-sandboxallownestedusernamespa","heading":"Device-tool refusal now names the nested user namespaces sandbox setting","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/device-tool-refusal-text-adds-sandboxallownestedusernamespa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Device-tool refusal now names the nested user namespaces sandbox setting\n\nThe message about device tools being withheld now lists `sandbox.allowNestedUserNamespaces` among the settings that weaken isolation\n\n**Unclear.** Whether turning on the setting now actually withholds device tools, or only the message text changed, is not clear.\n\n**What**\n\nWhen the sandbox (the fenced-off area where Claude Code runs commands with limits) has been weakened by a setting, the device serves no device tools and shows a message listing the settings that cause this. That list now includes `sandbox.allowNestedUserNamespaces`, placed between `sandbox.allowAppleEvents` and `sandbox.enableWeakerNestedSandbox`.\n\n**Why**\n\nIf you turn on `sandbox.allowNestedUserNamespaces`, expect it to count as weakening the sandbox, which can leave the device with no device tools.\n\n- Area: Sandbox\n- Names: `sandbox.allowNestedUserNamespaces`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}