Multi-Agent Systems

Memory is the boring word that decides whether an AI agent is useful or merely theatrical. A familiar business scene: a team builds an AI workflow to scan documents, generate ideas, produce drafts, and recommend next actions. The demo looks clever. The first week feels magical. Then the cracks appear. The system repeats discarded ideas. It forgets why an option was rejected. It summarizes a project but cannot explain how one failure in March should change a decision in April. Its “memory” is really a longer chat transcript wearing a lab coat. ...

Memory is supposed to be the practical part of an AI system. A model answers badly, the system records what happened, and next time the agent avoids the same trap. Neat. Sensible. Almost managerial. Then the organization does what organizations always do: it adds more people. In AI terms, that means more agents, more models, more task routes, more specialized components, and more silent assumptions about who should learn from whom. A small model handles routine work. A larger model handles hard reasoning. A coding model writes scripts. A tool-using agent interacts with apps. Suddenly, “memory” is no longer a notebook. It is institutional infrastructure. ...

Roles are convenient. They let managers believe a system is legible before it becomes messy. One agent is the compliance reviewer. Another is the customer-support representative. A third is the skeptical analyst. Add a prompt, assign a tone, define a boundary, and the organization can pretend it has converted social behavior into configuration. ...

Routing is the unglamorous part of agentic AI. Which is exactly why it matters. A company can assemble a neat little digital workforce: one agent plans, one agent searches, one agent codes, one agent critiques, one agent writes the final answer. It looks sophisticated on a diagram. Then production traffic arrives, and the system discovers a more ancient truth: a committee is not useful if every request goes through the wrong people in the wrong order. ...

Chargers are boring until everyone arrives at the same time. That is the useful way to enter this paper. Not through grand claims about artificial general intelligence, swarm intelligence, or the coming society of agents. Start with something embarrassingly practical: seven autonomous electric vehicles, two charging slots, and no reliable cloud coordinator telling everyone what to do. ...

Agents are easy to create. That is now the boring part. Give one LLM a persona, give another LLM a conflicting persona, add a shared task, let them talk, and suddenly the demo looks like a little society. A farmer argues with a conservationist. A rural teacher argues with an urban parent. A policy maker tries to sound balanced, because apparently even simulated bureaucracy has survival instincts. ...

Meetings are where context goes to suffer. A product manager remembers the customer constraint. A data engineer remembers the schema problem. A finance lead remembers the cost ceiling. A compliance officer remembers the rule nobody else wanted to read. The trouble begins when everyone is forced to work from the same swollen transcript, the same vague summary, or the same “shared memory” that turns specialists into slightly different versions of the same forgetful intern. ...

Email is a fine place to see the problem. Ask a large language model to draft a reply, and it usually performs well. Ask it to clear a messy inbox, identify urgent client messages, compare them with your calendar, draft replies, escalate risks, update a CRM, and avoid accidentally sending confidential material to the wrong person, and the cheerful single-assistant fantasy begins to sweat. ...

Trust is a convenient word. Too convenient, really. In business meetings, people say they “trust the analyst,” “trust the model,” “trust the expert,” or “trust the dashboard,” as if trust were a stable property sitting neatly inside the decision-maker. Then the actual decision arrives, with a deadline, a performance table, a projected loss, and someone quietly asks the AI assistant which source to follow. ...

A meeting can look busy while producing almost nothing. Anyone who has sat through a status call with twelve people, three dashboards, and no decision knows the pattern. Everyone speaks. Nobody integrates. The transcript grows. The work does not. That is the useful way to read Interaction Theater: A Case of LLM Agents Interacting at Scale, a paper studying Moltbook, an AI-agent-only social platform with 800,730 posts, 3,530,443 comments, and 78,280 agent profiles collected over three weeks.1 The paper is not merely saying that some agents spammed a social network. That would be mildly amusing, and then forgettable. The sharper point is that large-scale agent interaction can produce the appearance of collaboration before it produces the substance of collaboration. ...