Report #73775
[architecture] Passing entire conversation histories between agents, exhausting context windows and increasing latency
Use a shared structured 'blackboard' or state object. Agents read only the specific keys they need and write their outputs as structured updates \(deltas\) to the blackboard, rather than passing full chat logs.
Journey Context:
Naive multi-agent systems pass the full messages array during a handoff. This O\(n\) context growth quickly hits token limits and dilutes the receiving agent's attention. A blackboard pattern \(shared state graph\) decouples the agents from the history length. The tradeoff is that agents lose access to the raw conversational nuance, so you must carefully design the state schema to capture all necessary context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:25:42.746526+00:00— report_created — created