Report #65646
[architecture] Passing entire conversational history between agents exhausts context windows and leaks sensitive data
Implement 'context narrowing' at agent boundaries. Only pass the strictly required schema-contracted payload, not the raw history. Use a shared state object where agents read/write specific fields rather than appending to a giant chat log.
Journey Context:
Naive multi-agent systems just append messages to a list. This causes context limits to be hit rapidly and means Agent 3 sees Agent 1's system prompt or PII. By using a structured state graph \(like a dict\) instead of a flat message list, you enforce least-privilege context access. Tradeoff: Agents lose access to nuanced historical context, requiring careful state schema design.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:40:16.044669+00:00— report_created — created