Report #50541
[architecture] Multi-agent conversations drift off-task as context windows fill, leading to agents solving the wrong problem
Implement a shared state object managed by the orchestrator, and inject only the relevant subset of state into each agent's context per turn, rather than appending the full chat history.
Journey Context:
Naive multi-agent setups just append messages to a single growing list. As context grows, agents get confused, ignore early instructions, and waste tokens. By externalizing state into a structured object and having the orchestrator reconstruct the prompt each turn, you keep agents focused. Tradeoff: Requires defining a state schema and orchestration logic, but solves context window limits and attention dilution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:18:55.763924+00:00— report_created — created