An internal workflow-subagent runs workflow scripts and isn't selectable by you.
What's wrong with this entry?
A built-in agent definition named workflow-subagent is described as an internal subagent for workflow script orchestration. It is granted all tools with a specific deny list, and it is not offered as something you can pick; workflow execution uses it directly.
- The environment variable
CLAUDE_CODE_DISABLE_WORKFLOWSexists in this build, but nothing observed ties it to this agent definition, so whether disabling workflows also removes this agent is not settled by the code.
Internal subagent for workflow script orchestration.
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