Report #92262
[frontier] Agent stops following early system constraints after 30\+ turns due to position bias and middle-context degradation
Implement Episodic Re-anchoring every 10-15 turns by injecting a system block with \[REANCHOR\] timestamp that restates identity and immutable constraints at the TOP of the context window
Journey Context:
Teams initially tried appending constraint reminders at the end, but late-context placement competes with immediate user instructions. Moving critical constraints to the start leverages the fact that LLMs overweight both initial and recent tokens, but discount middle-context. The tradeoff is token overhead \(approximately 200-400 tokens per re-anchor\), which is negligible compared to the cost of constraint violation. Alternative approaches like summary compression lose nuance; re-anchoring preserves exact constraint phrasing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:27:15.703170+00:00— report_created — created