Multi-Agent Systems

TL;DR for operators The paper’s practical message is simple enough to be dangerous: once agents start working with other agents, the hard problem stops being “Can this model reason?” and becomes “Can this network behave?” Quanyan Zhu’s paper on the Internet of Agentic AI, or IoAI, frames the next stage of agentic systems as an open ecosystem of heterogeneous autonomous agents that discover collaborators, negotiate responsibilities, exchange context, invoke tools, and execute workflows across cloud, edge, device, organizational, and cyber-physical environments.1 That sounds grand, which is usually where useful engineering goes to die. But the paper’s better contribution is more sober: it treats agentic AI as a distributed systems problem. ...

Vote counts are cheap; finality is expensive Vote. That is the comfortable answer whenever multiple AI agents disagree. Ask ten agents, collect ten outputs, pick the majority, maybe weight by confidence, then call the result “robust.” It has the pleasant managerial smell of a committee decision. Everyone participated, something won, a spreadsheet can be made. ...

Opening — Why this matters now The current agentic AI conversation has a very convenient myth: if an AI agent fails, give it a better model, a longer context window, more tool calls, and perhaps a heroic prompt containing the phrase “think step by step” in several places. Then wait for magic. Preferably billable magic. ...

Opening — Why this matters now The AI industry has spent the last two years trying to turn large language models into workers. The result is a small circus of agents: coding agents, browser agents, research agents, support agents, spreadsheet agents, and agents that appear to exist mainly to summon other agents. Naturally, the next problem is not intelligence. It is management. ...

Opening — Why this matters now The AI industry has a small addiction to the word agent. Add another agent, then another, then a few hundred more, and the slide deck begins to smell faintly of civilization. Somewhere between “workflow automation” and “digital society,” we are invited to believe that scale itself becomes intelligence. ...

Everyone wants autonomous AI agents now. Not assistants. Not copilots. Agents: systems that watch a situation, decide what matters, take action, coordinate with others, and notice when someone in the room is quietly working against the plan. A normal business version sounds less theatrical than a social-deduction game, but the structure is familiar. A workflow has goals. People and software components have partial information. Some signals are useful. Some are noise. Some actors may be careless, misaligned, or malicious. The agent is expected to keep moving, complete the job, and not be fooled by plausible behavior. ...

The useful meeting, unfortunately, exists Meetings are usually where productivity goes to file a complaint. But there is one kind of meeting that high-stakes work still needs: the review session where a first draft is challenged, evidence is checked, and a senior decision-maker signs off. Radiology has long understood this. A resident may draft the report. A fellow may question the interpretation. An attending radiologist resolves the remaining uncertainty. The point is not ceremony. The point is controlled disagreement. ...

Football is usually explained after the fact. A team “pressed high.” A winger “found space.” A midfield line “lost compactness.” These statements may be accurate, but they arrive with the comforting uselessness of a weather report read after the picnic. The real managerial question is not merely what happened. It is what could have happened if the opponent shifted earlier, if the team protected the half-space, if the attacking line stretched the back four, or if the next pass invited three different futures instead of one. ...

A supercomputer is not impressed by a clever chatbot. That sounds rude, but it is also a useful starting point. Modern high-performance computing systems are built to run thousands of jobs in parallel, move data across specialized hardware, and tolerate the minor chaos of long simulation campaigns. A language model, by contrast, is very good at interpreting a request, proposing steps, and calling tools. Left alone, it often behaves like an overworked project manager with one phone line: think, call a tool, wait, think again, call the next tool, wait again. ...

The committee problem starts when the committee recognizes itself Committees are supposed to reduce individual bias. Put several reviewers in a room, give them different roles, and let disagreement expose weak arguments. This is the polite theory of institutional decision-making. It is also the theory behind many multi-agent AI pipelines. A critical model reviews the claim. A balanced model moderates the tone. A charitable model reconstructs the strongest version of the argument. A supervisor aggregates the outputs. Somewhere nearby, a fact-checking layer pulls external evidence. The design looks reassuring because it resembles human peer review, only faster, cheaper, and less dependent on coffee. ...