What probably matters to youSection of the release
What
The check that decides how session options such as permission mode, model, fallback model, effort, agent list, settings and appended system prompt are handled now also trips when CLAUDE_CODE_RESTRICTED is set in the environment, not only via --restricted. A new message states that cloud sessions cannot be created from a restricted session because they would not enforce the restriction.
Evidence
Cloud sessions cannot be created from a --restricted session: they would not enforce it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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 --restricted, on Tools reference.* A permissions [deny rule](/docs/en/permissions#match-all-uses-of-a-tool), the `--disallowedTools` flag, or [`--restricted`](/docs/en/cli-reference#cli-flags) removes `Bash` from the session.tools-referencesee 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 --restricted, on Tools reference.
Anthropic's release notes agreeAdded --restricted (or CLAUDE_CODE_RESTRICTED=1): removes the built-in tools that run commands or code and WebFetch (unless named in…
The name it cites is new in this buildNew in this build: --restricted
