points by refactor_master 3 hours ago | 0 comments
So this shows that people who appoint 50-agent "code factory studios" with Bob as the CEO, Alice as the CTO, ... is just a waste of tokens, compared to just asking one agent to write it all? It looks like your agents would internally just re-invent office politics, with 10 subagents writing to /tmp/chatter.md why it's unfair that Bob gets to lead.
[–] frankacter 3 hours ago
[–] beebmam 2 hours ago
> significantly optimizes accuracy, latency, and token consumption.
On what basis do you come to this conclusion with certainty?
[–] conception 3 hours ago
If you leave agents to figure it out, they will spend time figuring it out. If you give agents run-books and roles, they will align with the role at once.
[–] fnordpiglet 2 hours ago
See Conways law for how to mitigate this
[–] deadbabe 3 hours ago
Are you making a subtle reference to the Bobiverse series?
However, a multi-agent system (MAS) utilizing true separation of concerns, where each agent is equipped with highly scoped tool access, isolated knowledge bases (RAG), and defined operational constraints, significantly optimizes accuracy, latency, and token consumption.
In the referenced example, the agents share identical capabilities, toolsets, and context windows. As a result, there is no functional role differentiation, rendering the multi-agent architecture redundant.