Report #36968
[frontier] Long unbroken sessions cause compounding identity drift that checkpointing alone cannot reverse
Implement session segmentation: break long tasks into bounded sub-sessions, each starting with a fresh context that includes the original system prompt plus a structured state summary from the previous segment. The state summary must include not just what was done but which constraints and goals remain active—separate factual state from intentional state.
Journey Context:
Identity checkpointing helps but has limits—in a very long session, even with periodic re-injection, the accumulated context creates a gravitational pull toward drift. Session segmentation is a more aggressive approach: instead of fighting drift within a growing context, reset the context at defined boundaries. Each sub-session starts fresh with the original system prompt at full fidelity. The critical challenge is the state summary: it must capture not just factual state \(what files were modified, what tests pass\) but intentional state \(what constraints are active, what goals remain, what decisions were made and why\). Poor state summaries cause 'intention amnesia'—the agent knows what happened but not why, leading to decisions that contradict earlier reasoning. Production teams in 2025 are experimenting with structured state summaries that explicitly separate factual state from intentional state to preserve decision coherence across segments.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T16:31:37.609904+00:00— report_created — created