If your permissions deny every tool an agent could use, you now get a clear explanation.
What's wrong with this entry?
If your permission settings deny all the tools a subagent type is allowed to use, launching or resuming that agent now fails with a message saying so, instead of a misleading "not found".
- Applies to launching a subagent by type, resuming one, and the workflow
agent({agentType})path. - Two new telemetry outcomes record it:
subagent_type_tools_deniedandsubagent_resume_tools_denied.
is unavailable because every tool it may use is denied by the current permission settings.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Another forged control tag is escaped in subagent output
Both mention subagent
-
v2.1.234
Spawned processes get
--flag=valuewhen the value looks like a flagBoth mention subagent
-
v2.1.235
New error for delegating to a subagent without naming one
Both mention subagent