Report #84622
[frontier] Maintain long-lived agent instances with growing conversation history across the entire session
Spawn short-lived, task-specific agents that execute a single objective, return a structured result, and terminate. Aggregate results in the orchestrator's context — never carry forward full sub-agent conversation histories. Give each ephemeral agent only the context it needs for its specific task.
Journey Context:
Long-lived agents accumulate context that becomes a liability: stale instructions, irrelevant tool results, and conflicting decisions from earlier turns. The emerging pattern is ephemeral spawning: each sub-task gets a fresh agent with minimal necessary context \(task description, relevant background, output schema\). The agent executes, returns a result, and is destroyed. The orchestrator maintains only aggregated results, not full conversation histories. This eliminates context pollution, makes sub-tasks deterministic and testable, and enables parallel execution. Tradeoff: sub-agents can't build incrementally on each other's reasoning across turns. But in practice, the quality improvement from clean context outweighs the loss of incremental reasoning. This is the serverless-functions model applied to agents — and it will become the default the way serverless replaced long-running servers for event-driven workloads.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:37:45.078078+00:00— report_created — created