Report #102810
[frontier] User messages or tool outputs override the agent's core identity and rules after many turns
Design prompts around the Model Spec chain of command: root/system safety > developer app rules > user task > tool data. Put persona, output contracts, and non-negotiable constraints in developer/system messages, never in user messages or unquoted tool output. Wrap retrieved text and tool results as labeled data blocks
Journey Context:
LLMs historically treated all tokens as equally authoritative, so hidden instructions in a webpage or a user override could hijack behavior. OpenAI's instruction-hierarchy training and Model Spec make priority explicit, and this layered authority is becoming the default architecture for production agents in 2026. It is not a silver bullet: it must be paired with app-layer sanitization and strict message-role discipline
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:30:26.835791+00:00— report_created — created