You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
What
When Claude Code builds the settings for running an eval or a workflow, the disallowed_tools list from the base configuration and the one from the override are now combined. Before, the override's list replaced the base list.
Why
Tools blocked in a parent configuration stay blocked when an override adds its own list.
Read from
Names in the bundledisallowed_tools
Since it was published
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 disallowed_tools, on Subagents in the SDK.disallowed_tools=["Agent(fork)"],agent-sdk/subagentssee 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 disallowed_tools, on Subagents in the SDK.
Anthropic's release notes agreeAdded --disallow-tools and a disallowed_tools case field to claude plugin eval to keep specific built-in tools, such as Agent, out of eval…
