Report #58966
[architecture] Agent context window bleeds irrelevant state and instructions into downstream agents
Implement strict context filtering at handoff—only pass the exact JSON output of the previous agent's task, not its entire conversational history, unless explicitly required.
Journey Context:
Orchestrators often pass the full messages array from Agent A to Agent B to 'maintain context.' This is a mistake: Agent A's internal reasoning, failed attempts, and system prompt confuse Agent B and waste tokens. Agent B only needs the artifact Agent A produced. Tradeoff: Agent B loses the 'why' of Agent A's decision, but gains clarity and reduces hallucination risk from conflicting instructions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:27:57.137358+00:00— report_created — created