Report #85864
[frontier] Agent quality degrades irreversibly after 50\+ turns with no recovery path
Implement session checkpoint-restart: at task phase boundaries, have the agent produce a structured state summary \(decisions made, constraints active, current file state\), then restart the context with: original system prompt \+ structured summary \+ next task. The agent continues with fresh attention allocation.
Journey Context:
Appending context indefinitely doesn't scale because attention is a finite resource that dilutes across tokens. Starting completely fresh loses all context. Checkpoint-restart is the middle ground: compress the conversation into a summary, then restart. The critical insight is that the summary must be STRUCTURED, not narrative. A narrative summary \('we discussed the API design and decided on REST'\) doesn't preserve constraint salience — the constraint is buried in prose. A structured summary \('ACTIVE CONSTRAINT: use REST not GraphQL \| DECISION: endpoints follow /api/v2/ pattern \| CURRENT STATE: src/api/ created'\) preserves constraints as first-class objects that receive independent attention weight. Production teams in 2025 are implementing custom checkpoint logic that knows which constraint categories to preserve versus which decisions are finalized and can be dropped from the summary, keeping the restart context lean.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:42:26.516197+00:00— report_created — created