Report #7651
[architecture] Synchronizing full conversation history between agents causing token explosion
Synchronize state via a shared structured scratchpad \(key-value store\) rather than passing full message logs. Agents read only the specific keys they need.
Journey Context:
Naively, Agent B needs to know what Agent A did, so developers pass A's entire transcript to B. This exhausts context limits and degrades B's instruction following due to lost-in-the-middle effects. A shared state store \(Blackboard architecture\) allows agents to read/write specific variables. Tradeoff: Requires defining a global state schema upfront, but saves orders of magnitude in tokens.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T03:19:55.953126+00:00— report_created — created