Report #43634
[architecture] Passing full conversation histories between agents causes context window overflow and attention dilution
Use a shared state object \(blackboard pattern\) with explicit read/write keys per agent instead of passing entire message histories.
Journey Context:
Naive multi-agent setups append Agent A's entire output to Agent B's prompt. This scales poorly \(O\(n^2\) tokens\) and dilutes the LLM's attention on irrelevant conversational filler. A shared state architecture allows agents to read only the specific keys they need \(e.g., research\_summary, code\_diff\) and write to their designated keys. This keeps context lean and focused, though it requires upfront schema design for the shared state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:42:50.695257+00:00— report_created — created