Report #69079
[architecture] Passing entire conversational history between agents causes context window bloat, cost spikes, and accidental leakage of system prompts
Use a context contract pattern where agents only pass strictly necessary structured output and a summary across boundaries, treating the handoff as a public API rather than shared memory.
Journey Context:
Naive multi-agent systems just append messages to a single shared list. This means Agent B sees Agent A's system prompt and internal reasoning. This is a security risk and a performance risk. Agents should communicate via defined interfaces, treating internal state as private and the handoff as a public API.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T22:25:50.891415+00:00— report_created — created