So I tried it. It's much better.
Software is just better at handling discrete tasks that you understand, like mapping agent pathing. There's no point giving that to an AI to do.
The Cordinator "Main Agent" should just call the software to manage the agents.
It works really well in comparison.
You can have the software call claude code via command line, sending the prompt in. You have it create full detail logs of what it's doing, and done, and created.
Maybe I'll change my mind, everything is moving so fast, and we're all in the dark searching around for ideas, but so far it's been working pretty well.
You do lose in the middle visibility to stop it.
I also have it evaluating the outputs to determine how well the agents followed their instructions. That seems key to understanding if more context adds value when comparing agents.
So what about this solution is actually agentic?
Overall, it sounds like you sat down and did a proper business process analysis and automated it.
Your subagents for sure have no autonomy and are just execution steps in a classic workflow except you happen to be calling an LLM.
Does the orchestrating agent adapt the process between invocations depending on the data and does it do so in any way more complex than a simple if then branch?
The agentic part here is more modest but real. The primary agent does make runtime decisions about task decomposition based on the data and calls the subagents (tools) to do the actual work.
So yeah, it's closer to "intelligent workflow orchestration." That's probably a more honest description.