Report #80159
[architecture] Passing full conversation histories between specialized agents exhausts context windows and increases hallucination
Enforce a 'summarization boundary' where the outgoing agent must produce a structured state object containing only the necessary variables and a concise summary, discarding the raw token history.
Journey Context:
In multi-agent frameworks, it's tempting to just append messages to a single shared list. However, Agent C \(a deployer\) doesn't need the 50 messages of Agent A \(a researcher\) debating web search results. Passing full history wastes tokens, hits context limits, and introduces noise that causes the downstream agent to latch onto irrelevant historical details. The fix treats agents like microservices passing JSON payloads, not humans replying to a thread. Tradeoff: Loss of subtle context that might be relevant, but necessary for scalability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:08:49.540890+00:00— report_created — created