@hanakoxbt: your two agents are not collaborating. the second one is redoing the first one's work. it looks like teamwork in the tr…
Summary
Discusses a common failure in multi-agent LLM systems where handoff summaries lose evidence, causing duplicated work. Recommends passing artifacts (files, schemas, captured responses) instead of prose summaries to preserve context.
View Cached Full Text
Cached at: 08/04/26, 02:10 PM
your two agents are not collaborating.
the second one is redoing the first one’s work.
it looks like teamwork in the trace. two clean handoffs, one answer.
what actually happened is that agent A paid for six findings and agent B inherited one sentence.
two agents cannot share a window. that is not a framework limitation, it is the whole mechanism.
so the first one summarises, and the second one inherits the summary.
A read the docs, sent a null field, got a 400, tried the batch route, got a 404, and worked out that the endpoint wants ISO dates and an auth header.
five of those six findings cost a tool call.
what crosses is one line. use v2, ISO dates, no nulls.
the 400 does not cross. neither does the request that caused it, the response body, or the routes already ruled out.
why this is worse than a lossy summary
it is not that B distrusts the line. it believes it completely.
it is that a conclusion without its evidence cannot be reasoned from.
B has a sentence saying nulls are rejected. it does not have the failure that proves it, so the first time it hits an edge that sentence does not cover, it has nothing to work with.
and an agent with a gap does what any agent does. it goes and finds out.
finding out means the same doc read, the same null field, the same 400.
by the time B arrives where A already was, that stretch has been paid for twice.
what to actually do
pass artifacts, not prose. a file, a schema, a captured response. those survive the handoff intact, because they are not a description of evidence, they are the evidence.
write down what failed, not just what worked. the ruled-out paths are the part that stops the next agent walking them.
check who the summary is addressed to. one written for a human reads as a report. one written for the next agent reads as a spec, and they are different documents.
and before you split the work at all, ask what the second agent will need to have seen. if the answer is most of what the first one saw, you do not have two agents. you have one agent and an expensive amnesia.
this is also why measuring the final answer tells you nothing here. both runs end correct. the duplicated work is only visible in the trajectory.
save this - then read the eval setup below
Similar Articles
In practice, our multi-agent failures were almost never the model - they were the handoffs. Does the MAST data match what you see?
An analysis of multi-agent LLM pipeline failures, citing the Berkeley MAST paper which attributes most failures to coordination issues (specification, inter-agent misalignment) rather than model capability, and suggests dedicated verifier agents as a fix.
@rohit4verse: a databricks tech lead just spent 26 minutes on the part of multi-agent nobody wants to say out loud: your agents don't…
A Databricks tech lead argues that multi-agent AI systems fail not due to model intelligence but due to lack of coordination, framing 50+ agents as a distributed systems problem where parallelism is easy but shared coherence is difficult.
@UnTalNixon_exe: THE MOST COMMON ERROR IN MULTI-AGENT SYSTEMS ISN'T THE ONE YOU THINK It's not choosing the wrong model. It's not prompt…
The article discusses a Stanford paper that identifies information loss during handoffs as the most common error in multi-agent systems and presents architectures and a standard loop with shared memory, message schemas, observability, and guardrails to enhance performance.
@alex_prompter: Multi-agent AI setups break at four points. Routing misfires, parallelism never happens, handoffs lose context, and cov…
Multi-agent AI systems commonly fail at routing, parallelism, handoffs, and coverage. This post recommends a dispatch matrix, parallel execution, structured handoffs, and a catch-all fallback with logging to fix these issues.
The silent failure that wrecked two different multi-agent teams in exactly the same way
Two different multi-agent system teams experienced the same silent failure caused by agents writing to the same key in different formats, leading to phantom corruption. The article discusses solutions including schema validation, read-after-write validation, and introducing an 'unconfirmed' state for unverifiable actions.