Report #84865
[architecture] Exhausting context windows by duplicating full conversation histories across multiple agents
Use a shared structured state store \(e.g., a global scratchpad or key-value store\) and pass only references or IDs between agents, allowing them to fetch state on-demand.
Journey Context:
The naive approach to context sharing is appending the entire conversation history to every agent's prompt. This scales quadratically in token usage and quickly hits context limits. Decoupling the shared state from the conversational context—where agents read/write to a shared memory via tools—keeps prompts lean and synchronizes state without bloating the context window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:02:07.180161+00:00— report_created — created