Report #29629
[architecture] Context window overflow or hallucinated state from passing the entire conversation history between agents during handoffs
Use a structured scratchpad or shared state object that agents read from and write to, rather than injecting the raw transcript of previous agents into the next agent's prompt.
Journey Context:
When Agent A hands off to Agent B, developers often pass the full history. This quickly exceeds context limits and fills B's window with A's internal reasoning, which confuses B. Passing just the user query loses intermediate state. The solution is a shared structured state \(like a JSON object or database record\) that acts as a single source of truth. Agents receive the user query plus the current state object, perform their task, update the state object, and hand off. This keeps context lean and focused on facts, not process.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:07:22.313520+00:00— report_created — created