Report #35117
[frontier] Long agent sessions accumulate drift and lose coherence
Delegate discrete tasks to fresh sub-agent instances with clean context windows, passing only minimal required state. Use the orchestrator as a structured state keeper, not a conversational participant. Each sub-agent starts with zero drift.
Journey Context:
The default architecture is one agent, one long session, all context accumulated linearly. But every turn is an opportunity for drift—each message slightly shifts the agent's interpretation of its role. The emerging pattern in 2025 is 'orchestrator-worker': a thin orchestrator maintains session state in structured form \(not raw conversation\) and spawns fresh worker agents for each task or task cluster. Each worker gets a clean context with only the relevant constraints and task-specific context. The orchestrator never accumulates conversational drift because it doesn't converse—it routes. The tradeoff is overhead: each worker spawn costs a system prompt and context-reconstruction tokens. But this is the right call because drift is compounding \(each drift builds on the last\), making the cost of drift in a long session superlinear. Fresh contexts reset the drift clock to zero.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:24:52.694466+00:00— report_created — created