Report #79015
[frontier] Agent gradually stops following style, tone, and format constraints after 30\+ turns but still executes tasks correctly
Implement a 'constraint re-injection' layer that re-inserts a distilled version of soft constraints \(tone, style, format, scope\) as a system message every 15-20 turns. Hard constraints \(safety, core task logic\) rarely need re-injection because they are reinforced by task completion feedback loops.
Journey Context:
The key insight is the asymmetry between capabilities and constraints: every time an agent successfully completes a task, the capability pathway is reinforced in-context. Constraints, however, are only 'activated' when the agent considers violating them, which becomes less frequent as context grows. This is why your agent still writes perfect code at turn 50 but has completely abandoned the concise output format you specified at turn 1. Naive approaches try to solve this with longer system prompts, but longer prompts actually make the problem worse due to attention dilution across more tokens competing for the same attention budget. The frontier approach is periodic, targeted re-injection of only the constraints most prone to drift — typically style, tone, format, and scope boundaries. Production teams in 2025 are building middleware that automates this based on turn-count tracking.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:13:14.093994+00:00— report_created — created