This misses an important detail. In Claude Code [1], ultracode suggests the agent create a JavaScript code to deterministically orchestrate sub agents. This is different from just having the main agent launch sub agents and (non-deterministically) manage them.
The resulting workflow is called “dynamic” because CC creates this orchestration script dynamically, “on the fly”.
[1] https://claude.com/blog/introducing-dynamic-workflows-in-cla...
Another useful thing about dynamic workflows is you can ask Claude to make them durable as skills (or slash command) that can be invoked later.
I believe inside Google they have a similar concept called “deterministic workflows”.
I find ultracode extremely useful. Of course you have to watch how your 5 hour and weekly session usage percentages are getting used. So I had Claude make a status-line with 3 progress bars: for context window, 5h session, 7d session:
https://pchalasani.github.io/claude-code-tools/tools/statusl...
It’s sad to see folks like Karpathy make a big deal about looping, than to find that the loop command is broken and it’s crap vibe coded documentation isn’t even accurate on the Claude docs.
This whole dynamic workflow idea is on face bad. It’s all done as a massive cope for the fact that real determinism (I.e using structured outputs to enforce control flow of tools deterministically) is bad for alignment/safety so they can’t let you have access to those tools anymore…
https://github.com/openai/codex/blob/98d28aab54ed86714901b66...
https://github.com/openai/codex/blob/98d28aab54ed86714901b66...
https://github.com/openai/codex/blob/98d28aab54ed86714901b66...
The way I see it is that they try to normalize and ease the use of practices established by the community.