Report #54014
[architecture] Context window limits exceeded or costs explode when passing full conversation histories between agents
Implement a state contract where agents output only a strictly typed 'artifact' \(delta\) rather than their full scratchpad. The orchestrator maintains the global state and injects only the necessary artifacts into the next agent's context.
Journey Context:
Naive multi-agent systems pass the entire message list from Agent A to Agent B. This is O\(n^2\) in token usage and hits context limits fast. By enforcing an artifact-based contract, you bound the context size. Tradeoff: Agents lose access to intermediate reasoning steps, which might be needed for complex tasks. Mitigate by allowing agents to explicitly request specific historical artifacts from the orchestrator if needed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:09:37.154322+00:00— report_created — created