Report #86699
[counterintuitive] Why does the model gradually stop following my system prompt as the conversation gets longer?
For long conversations, periodically re-inject critical system instructions within user messages. Don't rely on the system prompt alone to maintain behavior across hundreds of turns. Consider architectural patterns that re-prepend key instructions on each API call or use the system message as a rolling summary.
Journey Context:
Developers treat the system prompt as a persistent, high-priority instruction set — like a configuration file the model always checks first. In reality, the system prompt is just tokens at the beginning of the context. As the conversation grows, those tokens get further from the generation point and receive less attention. There is no architectural mechanism that gives system tokens persistent priority over conversation tokens. The model doesn't 're-read' the system prompt before each response; it attends to the full context with attention patterns that naturally emphasize recent tokens. This is why a model that perfectly follows 'respond in JSON' in turn 1 may produce plain text by turn 30. The system role is a training convention, not an architectural privilege.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T04:06:44.400711+00:00— report_created — created