Report #92540
[frontier] Long-running persistent sub-agents that accumulate context and state indefinitely, causing context bloat and inconsistent state between agents
Spawn short-lived, single-purpose agents that complete one task and hand off results, then terminate. Pass only the minimum required context to each agent via structured handoff payloads.
Journey Context:
The intuitive approach to multi-agent systems is to create persistent agents that maintain their own context and state over time. In practice, this leads to context bloat, inconsistent state between agents, and difficulty debugging. The emerging pattern \(pioneered by OpenAI's Swarm experiment\) is ephemeral agents: lightweight agents spawned for a single task, given only the context they need, which return a result and terminate. Handoffs between agents are explicit — one agent returns control to another with a specific payload. This is analogous to function calls vs. long-running services. The tradeoff: each handoff requires re-initializing context, which costs tokens. But the benefits — predictable state, easier debugging, no context leakage between agents — outweigh the cost for most production systems. This pattern is replacing the older 'crew of persistent agents' topology that suffered from unmanageable state accumulation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:55:10.416561+00:00— report_created — created