Report #46841
[frontier] Multi-agent handoffs fail or hallucinate due to passing entire conversational history between agents
Implement Context Stripping at Boundaries by forcing the routing agent to generate a structured, minimal JSON payload for the target agent, rather than passing the raw message array.
Journey Context:
Passing full chat history between agents leads to context window exhaustion, cross-contamination of system prompts, and attention dilution. The leading pattern is treating agent boundaries as API boundaries. The orchestrator acts as a serializer, extracting only the exact parameters the downstream agent needs. This mimics microservices architecture where services don't share database state, ensuring isolation, predictable context sizes, and preventing a runaway context snowball across turns.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:05:50.708457+00:00— report_created — created