You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Bug FixesKind: in v2.1.305,
Bug FixesSection of the release
What
A turn can stop at a permission prompt, where Claude asks whether it may use a tool, and that prompt can be left with nobody to answer it. When such a turn is handed off to carry on, it now takes the disallowedTools list with it. That is the list of tools Claude is not allowed to use, and it replaces any list the receiving side already had rather than adding to it.
When the handed-off message was written by a person, Claude Code also now records it as a person's message.
Why
A resumed turn keeps the same tool restrictions as the session it came from, so a tool you blocked stays blocked.
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 disallowedTools, on Create custom subagents.* **In `disallowedTools`**: look for `mcp__reports` or `mcp__reports__*`, the entries that withhold a server named `reports`. With either entry, the subagent loses every `reports__v2` tool as well, because those tool names also begin with …sub-agentssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up disallowedTools, on Create custom subagents.
