Report #71481
[architecture] Hitting token limits and high latency from passing entire conversation histories between agents
Use a shared structured state object \(a blackboard or scratchpad\) that agents read from and write to, rather than passing full message logs.
Journey Context:
Naive multi-agent orchestration appends the entire conversation history to the next agent's prompt. This exponentially consumes tokens and cross-contaminates system prompts. A shared state object decouples the agents from the conversation history. Agents only read the specific state keys they need and append their results, keeping the context window lean and focused.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:33:39.708365+00:00— report_created — created