What probably matters to youSection of the release
What
The sandbox.allowNestedUserNamespaces setting lets commands inside the sandbox create their own user namespaces, a Linux feature some programs use to fence themselves off. Its description now:
covers WSL (Windows Subsystem for Linux) as well as Linux
lists Chromium and Electron apps, rootless podman and buildah, a nested bubblewrap, and unshare as tools that need it
warns that turning it on removes the sandbox's isolation of the code it runs
It remains off by default. When Claude Code runs commands through /bin/sh in the sandbox, it now explicitly turns nested user namespaces off.
Why
The setting is a way to let rootless containers and Chromium-based tools run inside the sandbox, at a stated security cost. Turn it on only when such a tool fails without it.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up sandbox.allowNestedUserNamespaces, on Configure the sandboxed Bash tool.* To keep Chromium's or Electron's own sandbox, or to run a nested bubblewrap or `unshare`, set [`sandbox.allowNestedUserNamespaces`](/docs/en/settings-reference#sandbox-allownestedusernamespaces) to `true` in `~/.claude/settings.json`, no…sandboxingsee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up sandbox.allowNestedUserNamespaces, on Configure the sandboxed Bash tool.
Anthropic's release notes agreeAdded sandbox.allowNestedUserNamespaces so sandboxed commands on Linux can create user namespaces (Chromium, rootless podman); this lets…