Report #52415
[frontier] Agent ignores specific instructions despite them being clearly stated in the system prompt
Use structural positioning to weight instructions by importance: \(1\) first position for identity definition, \(2\) last position before user input for task-critical constraints, \(3\) XML tags to create attention-attracting boundaries around key rules, \(4\) middle sections for examples and context that can tolerate partial attention loss.
Journey Context:
Research consistently shows that position within the prompt dramatically affects adherence. The common mistake is treating the system prompt as a document to be read linearly with uniform attention. In reality, the model processes it with a strong positional bias: high attention at the start, a dip in the middle, and a spike at the end \(recency\). Teams waste effort strengthening middle-positioned instructions with formatting tricks—ALL CAPS, bold, exclamation marks—which can backfire by making text seem less coherent. The right approach is to work with the positional bias rather than against it. XML tags are particularly effective because they create structural boundaries that the model has been trained to attend to \(from training on structured data\). Place your most critical, most-often-violated constraint immediately before where the user message will appear, exploiting recency bias at the exact point where the model generates its response.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:28:22.996149+00:00— report_created — created