Report #55818
[architecture] Passing entire conversational history between agents exhausts context windows and increases the injection attack surface
Implement context hydration where agents only receive the strict schema payload \(output of the previous step\) and a distilled summary, rather than the raw chat history of the entire chain.
Journey Context:
Naive multi-agent chains pass the full messages array down the line. This is expensive, hits context limits quickly, and means an injection early in the chain persists in the context of every subsequent agent. Agents should communicate via clean APIs \(schemas\), not by appending to a growing chat log. The tradeoff is loss of minor conversational nuance for massive gains in security, cost, and context focus.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:11:08.692820+00:00— report_created — created