Unclear The finding does not say which feature starts these sessions or whether that path runs in this build.
What
Claude Code can start another session and hand it some settings. The settings it hands over changed in two ways:
disallowedToolsis now included whenever it is not empty. It lists the tools the session may not use.effortis now read from the correct settings object. Before, it was read from the wrong one.
Why
A session started this way now keeps your blocked tools and gets the effort level that was meant for it.
Names in the bundledisallowedTools
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.
Added since
A small documentation edit on Create custom subagents touched a line naming disallowedTools after this was published.
The full content of each listed skill is injected into the subagent's context at startup, up to the first 32 distinct names in the list. This field controls which skills are preloaded, not which skills the subagent can access: without it, …sub-agents see the edit
Confirmed since
Anthropic's documentation has since written up disallowedTools, on Claude Code changelog.
* Fixed agent teams: a plugin-defined agent spawned by name now runs with its own prompt, tools, disallowedTools and effort instead of the defaultschangelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say which feature starts these sessions or whether that path runs in this build.
Anthropic's documentation agrees
Anthropic's documentation has since written up disallowedTools, on Claude Code changelog.