Report #95732
[frontier] Agent behavior degrades irreversibly after context window fills past 70%
Implement identity-aware session checkpointing: at 60-70% context utilization, generate a structured handoff document that explicitly restates agent identity, active constraints, accumulated decisions, and any constraint exceptions granted. Start a fresh session with this document as the foundational context.
Journey Context:
Standard conversation summarization preserves 'what happened' \(decisions, code changes, user preferences\) while losing 'who I am' \(identity, constraints, behavioral rules\). This is because summarization naturally prioritizes factual content over meta-instructions. The frontier practice in 2025 is the identity-aware checkpoint—a handoff document with explicit sections for identity restatement and constraint inventory. Key insight: you must also transfer 'constraint exceptions'—instances where the user explicitly allowed the agent to violate a rule. Without these, the new session either re-enforces rules the user already relaxed, or the agent senses inconsistency and becomes confused. The tradeoff is that checkpoint generation itself consumes a turn and tokens, and poorly structured checkpoints can introduce new drift. Use a fixed template: , , , , .
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:16:15.201232+00:00— report_created — created