Multi-Agent Systems

A browser agent does not usually fail like a heroic machine confronting the limits of intelligence. It fails like an intern on a badly designed website. It opens the wrong listing. It misses the tiny sort option. It clicks around because the page has too much visual noise and not enough obvious structure. It sees the button but not the pattern. Then, because the agent has no lasting operational memory of the stumble, the next task sends it back into the same swamp with a fresh pair of shoes. ...

Enterprise AI teams love an architecture diagram. Boxes, arrows, specialist agents, memory stores, tool registries, a tasteful orchestrator sitting at the top like a middle manager with JSON access. It looks reassuring. It looks intentional. It also looks suspiciously like the kind of thing that can fail in six different places while still producing a beautifully formatted answer. ...

Tickets are not equal. Some user requests are glorified form-filling. Some are ambiguous investigations with missing context, tool calls, intermediate checks, and enough failure modes to keep a compliance officer quietly blinking at the ceiling. Yet many agentic systems still behave as if every query deserves the same ritual: summon the agents, run the workflow, pass outputs around, maybe add a debate round for theatrical effect, and hope the bill does not look too much like modern art. ...

A bad agent stack often looks suspiciously like a bad committee. One agent proposes a plan. Another wanders into a neighbouring topic. A third confidently supplies a detail that is almost right, which is a particularly expensive genre of wrong. Then the system fuses the outputs, declares victory, and leaves the human operator to discover that “collaboration” was just error propagation wearing a nicer blazer. ...

Queue. That is still the hidden operating model of much modern science. Queue for the instrument. Queue for the simulation. Queue for the data transfer. Queue for a human to inspect the result, change the parameters, approve the next run, and remind three systems with incompatible interfaces that they are supposed to be part of the same experiment. The glamour version is “AI for discovery.” The operational version is a researcher quietly becoming a logistics coordinator with a PhD. ...

Budgets are where autonomy becomes real. A chatbot can be annoying. An agent with a procurement account, API access, calendar authority, cloud credits, and a habit of negotiating with other agents is something else entirely. At that point, we are no longer discussing “workflow automation” in the tidy enterprise sense. We are discussing economic actors: software systems that request resources, trade off priorities, outsource tasks, pay for services, and generate consequences faster than the compliance department can ask for a meeting. ...

Every agent platform eventually develops a storage problem and pretends it is a memory strategy. The logs are all there: user turns, tool calls, partial plans, failed attempts, corrected answers, retry traces, database lookups, compliance notes, and the occasional heroic workaround that actually solved something. The tempting move is obvious. Store everything. Embed everything. Retrieve whatever looks semantically close. Then call it “long-term memory,” because “expensive junk drawer with cosine similarity” sounds less fundable. ...

Repositories are where useful software goes to become someone else’s setup problem. Every company has lived some version of this. A team finds a promising GitHub repository. The README looks confident. The demo works on the author’s laptop, naturally. Then the actual work begins: dependency pinning, missing model weights, obscure data formats, broken examples, undocumented entry points, and the strange ritual of reading three GitHub issues from 2022 to discover the one command that still works. ...

Kernel Kombat: How Multi-Agent LLMs Squeeze 1.32× More From Your GPUs GPU bills have a charming way of turning “just one more model deployment” into a finance meeting. For companies running large language model serving stacks, the problem is rarely that nobody knows GPUs matter. Everyone knows. The harder problem is that performance bottlenecks often live inside kernels most executives will never see: attention merges, normalization fusions, activation multiplications, tiny pieces of code called millions or billions of times until “small inefficiency” becomes “why is the infrastructure budget wearing a crown?” ...

TL;DR for operators Personal health AI is usually sold as a friendly chatbot with a fitness tracker bolted on. This paper argues for something more awkward, more expensive, and much more plausible: a coordinated system of specialised agents. One agent analyses longitudinal wearable and health-record data. One grounds advice in health knowledge and user context. One handles coaching, goal-setting, and behaviour change. An orchestrator decides who should act, who should support, what should be remembered, and how the final answer should be assembled.1 ...