Report #102816
[frontier] Agent starts ignoring system-level instructions after only a few turns
Keep the most critical constraints in a short, repeated developer/system message and place them near the end of the active context window. For self-hosted models, consider attention-budget methods that reserve attention mass for system prompts; for API agents, rely on periodic re-injection and compact restatement rather than a single long prompt
Journey Context:
Empirical work quantifies instruction instability: popular models show significant drift within eight self-chat rounds, linked to attention decay over long exchanges. Split-softmax directly addresses this mechanism. In API-only settings you cannot modify attention, so architectural mitigations become prompt-placement and re-injection discipline. Leading agent frameworks now re-inject the active plan on every turn instead of assuming the system prompt remains salient
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:30:37.891200+00:00— report_created — created