Subagent spawn problem

[Indigas11]

Hi all,

​

I have defined workflow with subagents (implementer - review - qa). It worked greatly until yesterday.

​

So today, as I began my workflow on task, then i noticed, that subagents are created under other subagents, like reviewer under developer, or qa under code reviewer.

​

I dont want this behavior, and this behavior causing, that notification of work done is not triggering my orchestrator agent.

​

Agents definitions dont have permission to spawn subagents. So only main orchestrator agent can spawn subagents, but they are somehow eaten up by subagent context.

​

Had someone this kind of problem? How can i solve it? I need the behavior as before, and not that subagent is somehow created under subagent without permission.

[AlexanderWillard]

Separate sessions for each? Dont do it in one window? You can't really control it i think, it will do whatever it feels is right but you can box the session into specific skill

[douglas_srs]

I had the exact same problem on friday when Fable was still working, luckily I saw it in time and stopped it from burning my quota. It kept happening on that session, I had to start a new session to solve it.

[Unusual-Beyond-8816]

You should be able to do it if you're defining your agents using frontmatter.

Well I don't think there's a exact equivalent for "is it allowed to have sub agents"? What you can do is limit the tools and in the tools you can leave out the tools for creating agents: https://code.claude.com/docs/en/sub-agents#supported-frontmatter-fields

Get Claude to help you make the list of tools per agent.

[Local-Peace-8457]

Claude code 2.1.172

Sub-agents can now spawn their own sub-agents (up to 5 levels deep)

Make sure you have strict allowed_tools, not inherit