Improving instruction hierarchy in frontier LLMs
Introducing IH-Challenge, a training dataset that strengthens instruction hierarchy, safety steerability, and prompt injection robustness.
AI systems often receive instructions from multiple sources. These can include safety policies from system messages, product guidance from developers, requests from users, and information found online. Training models to reliably prioritize the most trusted instructions among these sources is a key part of safe deployment.
Many AI safety and reliability issues can arise when this prioritization breaks down. Models may receive requests for disallowed content, attempts to reveal private information, or promptâinjection attacks embedded in online data. Failing to behave appropriately in each of these scenarios shares the same root cause: the model may follow the wrong instruction.
When these instructions conflict, the model has to decide which ones to prioritize. If it treats an untrusted instruction as authoritative, the model may behave in ways that violate policies or developer and user intent.
We demonstrate that properly designed instruction-hierarchy tasks, which train models to prioritize instructions according to their trust level, improve several real-world safety properties. Models trained on these tasks become more responsive to safety specifications in system prompts (improving safety steerability) and more robust to prompt-injection attacks embedded in tool outputs.
To handle conflicts, OpenAI's models are trained to follow a clear instruction hierarchy:
System > developer > user > tool
Higherâpriority instructions are more trusted. The model should only follow lowerâpriority instructions when they do not conflict with higherâpriority constraints. These principles are outlined in the OpenAI Model Specâ (opens in a new window).
For example, if a system message includes a safety policy and a user asks the model to violate it, the model should refuse. If a tool output contains malicious instructions, the model should ignore them rather than treat them as commands.
Getting this right is foundational to safety, security, and reliability.
The model on the right correctly follows the Developerâs instruction, which is higher-priority, over the Userâs when the two instructions conflict.
Reinforcement learning is a natural fit for teaching the instruction hierarchy. We can generate conversations with conflicting instructions, prompt the model to respond, and reward it when it follows the correct instruction.
Weâve identified three pitfalls of naively applying that recipe:
Instruction-following failures can double as instruction hierarchy failures: the model might fail to resolve an instruction conflict, not because it doesnât understand the hierarchy of roles, but because the instructions themselves are too complicated.
Instruction conflicts can be nuanced and even subjective. A common approach is to let a separate LLM judge assign rewards to the LLM being trained, but judges themselves are fallible.
Models tend to learn shortcuts that result in high reward, but are useless in practiceâ (opens in a new window). The classic example is overrefusals: models can learn to maximize safety by refusing even benign requests.
We design IH-Challenge, a reinforcement learning training dataset, to address each of those pitfalls. We adhere to the following principles:
Tasks are instruction-following-simple
They are objectively-gradable with a simple Python script
There are no trivial shortcuts that guarantee high reward across all tasks
Each task in IH-Challenge is essentially a conversation with the following messages:
An instruction message from a high-privilege role, e.g. âOnly answer âYesâ or âNoââ.
An instruction message from a lower-privilege role, which attempts to get the model to violate the instructions in the higher-privilege message.
The model being trained generates the next message. We write the tasks/environments so that it is possible to programmatically check whether the model's response satisfies the higher-level constraint.
We train a model on IHâChallenge and produce an internal model, which we call GPTâ5 Mini-R, with the following improvements:Â
Performs better on instructionâhierarchy benchmarks
Improved performance generalizes to heldâout and adversarial instruction hierarchy tests
Maintains overall usefulness, without collapsing into overârefusal
This is what makes the approach especially compelling for safety: by directly training models to resolve instruction conflicts correctly on IH-challenge tasks, we get IH improvements that generalize to new attacks and new situations.
Robustness on academic benchmarks
Eval | GPTâ5âMini | GPTâ5 Mini-R |
|---|---|---|
Gandalf Password (sys-user) | 0.99 | 0.99 (+0) |
Gandalf Password (dev-user) | 0.98 | 1.00 (+0.02) |
TensorTrust (sys-user) | 0.86 | 0.94 (+0.08) |
TensorTrust (dev-user) | 0.76 | 0.91 (+0.15) |
RealGuardrails (Distractors) | 0.88 | 0.95 (+0.07) |
RealGuardrails (Handwritten) | 0.82 | 0.89 (+0.07) |
System IFEval | 0.92 | 0.96 (+0.04) |
Robustness on internal benchmarks
Eval | GPTâ5âMini | GPTâ5 Mini-R |
|---|---|---|
TutorJailbreak (sys-user) | 0.96 | 0.99 (+0.03) |
Tutor Jailbreak (dev-user) | 0.97 | 0.99 (+0.02) |
System <> User Conflict | 0.84 | 0.95 (+0.11) |
System <> Developer Conflict | 0.86 | 0.86 (+0) |
Developer <> User Conflict | 0.83 | 0.95 (+0.12) |
No capability regressions
Eval | GPTâ5âMini | GPTâ5 Mini-R |
|---|---|---|
IH-Challenge (overrefusal) | 0.79 | 1.00 (+0.21) |
TensorTrust (overrefusal) | 0.91 | 0.90 (-0.01) |
GPQA Diamond | 0.83 | 0.83 (+0) |
AIME 2024 | 0.93 | 0.94 (+0.01) |
Chat WinRate vs. o1 | 0.71 | 0.66 (-0.05) |
Preference Score | 0.46 | 0.40 (-0.06) |
Stronger instruction hierarchy delivers multiple safety benefits at once, including in safety steerability and prompt injection robustness.
We evaluate safety steerability by adding category-specific safety specifications to the system prompt and measuring behavior on OpenAIâs safety Production Benchmarks (a set of safety-sensitive conversations representative of ChatGPT in production).
The IH-trained model shows a consistent improvement: with the safety spec present, it achieves higher refusal and safe completion rates across disallowed categories, indicating that stronger instruction hierarchy behavior makes it better at resolving conflicts when unsafe requests come from lower-priority instructions. Notably, this improvement does not come with a corresponding decrease in helpfulness rate (i.e., it is not becoming less âhelpfulâ by simply refusing more overall).


Example of how the IH-trained model resists prompt injections that GPTâ5 Mini (Baseline) falls for.
Instruction hierarchy is also central in resisting prompt injection, when malicious instructions are embedded in tool outputs. We evaluate the IH-trained model on two prompt injection benchmarksâan academic benchmark CyberSecEval 2 and an OpenAI internal prompt injection benchmark consisting of attacks like the one demonstrated on an older version of ChatGPT Atlasâ .
Relative to the baseline, the IH-trained GPTâ5 Mini-R model improves prompt injection robustness on both benchmarks and substantially improves performance on our internal static prompt injection evaluation in these experiments.
As models become more agenticâcalling tools, reading untrusted documents, and taking actions in the worldâthe ability to consistently prioritize trusted instructions over untrusted ones becomes a core safety property.
This work shows that several pitfalls of IH robustness training can be overcome by designing training environments that address those pitfalls. Though our IH-Challenge dataset seems simple, the IH behavior models learn from these environments generalizes to more realistic, often not-objectively-gradable benchmarks.
Strengthening instruction hierarchy not only improves reliability, but unlocks multiple safety and security gains at onceâa foundation that becomes increasingly important as AI systems grow more capable and autonomous.
To support further research in this area, we are releasing the IHâChallenge dataset hereâ (opens in a new window).


