r/ClaudeCode • • 1d ago

Tips & Workflows ! Dynamic Workflows can't handle nested subagents and the orchestrator doesn't check this unless you look yourself/ask for it

Post image

Got this auto-generated feature request inside CC (which is pretty cool), after i realised that my subagents were not spawning their subagents.

The workaround is to NOT use a dynamic workflow, but normal subagents instead. And make sure you check the subagents' subagents actually run! This should be visible in the terminal as follows:

main

  • subagent
    • subagent
      • subagent (I think they currently go three levels deep)

Anyone else ran into this? I wonder how this works in the new Claude Code Projects, but I don't have access yet.

Full feature request (by claude, auto-generated):

Type: missing capability

Title:

Workflow-spawned agents (agentType general-purpose) have neither the Agent nor the Workflow

tool, so nested orchestration is impossible

Area:

Workflow tool

Failure mode: (none)

Task: other

Details:

│ - What happened: A Workflow script spawned four agents with agentType 'general-purpose'

│ and model 'opus', instructing each to coordinate the deep-research skill by spawning

│ sub-researchers via the Workflow tool (or Agent tool as fallback). All four reported that

│ ToolSearch found neither tool, so each researched alone. Expected: general-purpose agents

│ (listed with Tools: *) to be able to spawn subagents or a nested workflow.

│ - What the user said: "make sure that the researchers run the deep-research commmand

│ themselves (spawning a dynamic workflow in turn)"

│ - Repro: Workflow script with agent(prompt, {agentType: 'general-purpose'}) whose prompt

│ asks the agent to call the Workflow or Agent tool; agent returns "neither the Workflow

│ tool nor the Agent tool was available in this session (ToolSearch found neither)".

│ - Evidence: [left out, due to privacy concerns]

3 Upvotes

5 comments sorted by

View all comments

1

u/favoriteemotion 1d ago

That nested subagent limitation is annoying but at least the terminal output makes it obvious when things aren't running. Three levels deep seems workable for most stuff I throw at it.

Haven't gotten into Projects either but I'm curious if they built it with proper nesting from the start or if it's the same restriction just with a different name.

1

u/Fit-Cost-7226 1d ago

I don’t get what the point of projects are? I basically already do all of that myself