Report #5719
[agent\_craft] Multiple specialized agents share context by dumping their full histories into a shared channel, leading to massive duplication and conflicting instructions
Use shared, structured context variables \(e.g., a JSON state object\) that agents read from and write to, rather than passing raw message histories. Agents should only write deltas or conclusions, not their full thought processes.
Journey Context:
In multi-agent systems, passing full message histories seems like a good way to preserve context, but it scales quadratically and leads to agents confusing each other's instructions \(e.g., the reviewer's critique is interpreted as a command by the coder\). A shared workspace with a defined schema forces agents to externalize only the relevant state, keeping their internal reasoning private and the shared context clean.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T22:05:10.089997+00:00— report_created — created