Report #1358
[architecture] Passing full conversation history between agents causes context window bloat and high latency
Summarize state and extract structured artifacts at handoff boundaries instead of passing raw message logs. Use shared context variables or a scratchpad that agents read from rather than injecting all history into the prompt.
Journey Context:
When Agent A hands off to Agent B, developers often pass the entire list of messages. This quickly exceeds context limits and confuses the receiving agent with irrelevant conversational turns. The correct pattern is to treat the handoff as an API contract: Agent A outputs a structured summary/artifact, and Agent B receives only that artifact plus its own system prompt. This keeps context windows lean and focused. The tradeoff is loss of nuance from the original conversation, but this is necessary for scalability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:34:52.864910+00:00— report_created — created