TBH, this one is an example of the rather good bucket, Id say?
I have seen much much worse examples on corporate blogs for example, where I question if authors even understand how to use any publishing system and how colors & info architecture works :-D
Sub agents are significantly more useful than multi agents.
Wrap a nested prompt with a tool call that is invoked by the caller prompt. That is the answer to all your suffering. You can repeat this for as many layers of invocation as you desire. You can layer determinism and non-determinism as much as you like in whatever orders you see fit with additional alignment, retry policies, logging, etc.
Agents running concurrently will not go any faster than one well-designed hierarchical agent system.
Imagine the simple task of incrementing a global counter. That would be my #1 benchmark. If you can demonstrate a MAS can increment that counter faster than a single agent can (monotonically without skipping), then I will happily delete 100% of the AI-related code I've authored and start over using your ideas.
What harness are you using? In both Claude Code and Codex I run into the issue of subagents being unable to dispatch their own subagents, so I haven't been able to play with "many layers of invocation".
If you leave "The Honest Summary" in anything Claude wrote, I am not going to read any of it, shows a complete lack of care or interest in what you are doing.
I don't care if you are having Claude write something for you, but I feel like I spent more time writing these two sentences than this person put into this post.
Perhaps I'm being uncharitable, but when I open up a page that was obviously created by Claude, I just close it again.
TBH, this one is an example of the rather good bucket, Id say?
I have seen much much worse examples on corporate blogs for example, where I question if authors even understand how to use any publishing system and how colors & info architecture works :-D
Sub agents are significantly more useful than multi agents.
Wrap a nested prompt with a tool call that is invoked by the caller prompt. That is the answer to all your suffering. You can repeat this for as many layers of invocation as you desire. You can layer determinism and non-determinism as much as you like in whatever orders you see fit with additional alignment, retry policies, logging, etc.
Agents running concurrently will not go any faster than one well-designed hierarchical agent system.
Imagine the simple task of incrementing a global counter. That would be my #1 benchmark. If you can demonstrate a MAS can increment that counter faster than a single agent can (monotonically without skipping), then I will happily delete 100% of the AI-related code I've authored and start over using your ideas.
What harness are you using? In both Claude Code and Codex I run into the issue of subagents being unable to dispatch their own subagents, so I haven't been able to play with "many layers of invocation".
depends on what type of problem it is
I am curious if we have any examples of problems that can only be solved via multiple concurrent prompts coordinating in real time.
Does anyone else open sites with this default claude code theme and immediately close them?
If you leave "The Honest Summary" in anything Claude wrote, I am not going to read any of it, shows a complete lack of care or interest in what you are doing.
I don't care if you are having Claude write something for you, but I feel like I spent more time writing these two sentences than this person put into this post.