Report #83925
[frontier] Single long-running sessions become 'polluted' with accumulated context, making agents unpredictable; restarting loses state
Implement 'session mitosis'—when context entropy exceeds threshold, fork into two sessions: one 'legacy' \(read-only reference\) and one 'active' \(pruned continuation\), with periodic reconciliation via message passing
Journey Context:
Teams face a dilemma: long sessions drift unpredictably, but restarting loses the 'understanding' built up through interaction history. Simple 'summarize and restart' loses nuance. Session mitosis treats the agent state like biological cells—when a session grows too complex \(measured by vector distance between current and original system prompt embeddings exceeding epsilon\), it splits. The 'legacy' session remains available as a read-only knowledge base that the 'active' session can query via tool calls, but doesn't carry forward the accumulated drift. This creates generational garbage collection for agent context, allowing indefinite operation without pollution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:27:33.657072+00:00— report_created — created