Report #46280
[frontier] Agent forgets formatting and tone constraints but retains core capabilities over long sessions
Implement a 'constraint hierarchy' in your system prompt. Place identity-critical constraints \(what NOT to do\) at both the very beginning AND very end of your system prompt. For long sessions, periodically re-inject a compressed version of your top-tier constraints as a system-level message every 15-20 turns. Never bury constraints in the middle of a long system prompt.
Journey Context:
The fundamental asymmetry is that capabilities are reinforced by training data \(the model already knows how to write code\), while constraints are thin overlays. Over a long session, every successful tool call reinforces capability, but nothing naturally reinforces the constraint. Teams try making system prompts longer and more detailed, but this makes drift WORSE because of the 'lost in the middle' problem — information in the middle of long contexts gets less attention. The right approach is counterintuitive: shorter, repeated constraint injections beat one comprehensive system prompt. Production teams in 2025 are moving toward 'constraint bookmarking' — placing the same constraint at multiple attention-weighted positions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:09:18.491547+00:00— report_created — created