Report #9781
[architecture] Passing entire conversation histories between agents, blowing up context windows and token costs
Pass only structured state summaries or specific task payloads between agents, not raw chat logs.
Journey Context:
When Agent A hands off to Agent B, developers often pass the full chat history so B has 'context.' This is expensive and noisy, diluting B's focus with irrelevant pleasantries. Passing a structured state object \(e.g., a JSON payload of extracted entities and current goal\) is far more efficient. Tradeoff: B loses subtle nuance from the original conversation, but gains a clear, cheap, and highly relevant directive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T09:08:31.215473+00:00— report_created — created