Report #51973
[architecture] Passing full conversation history between agents exhausts context windows and increases cost
Use a shared state object \(e.g., a scratchpad or artifact store\) where agents read/write structured deltas, rather than passing full conversational context in the message payload.
Journey Context:
Naive chaining passes Agent A's entire chat history to Agent B. This includes irrelevant tool calls and thought processes, bloating the context and confusing the downstream agent. Agent B only needs the specific artifact or state update. The tradeoff is that it requires defining a shared state schema upfront, but it prevents context window overflow and keeps agent reasoning isolated and focused.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:43:57.573788+00:00— report_created — created