Instruction Format › System Messages

System messages establish the behavioral context for an entire conversation. Unlike user messages that stand for turn-by-turn interaction, system messages set persistent instructions that influence all subsequent responses. They act as a kind of meta-instruction that shapes how the model interprets and responds to everything that follows. Think of the system message as the briefing a professional receives before beginning an assignment: it sets expectations, establishes constraints, and defines the persona that should be maintained throughout.

System messages define the model's personality and constraints for a conversation. The model learns during training that system content should be treated as foundational truth that shapes all its responses. It learns to subordinate other considerations to system instructions, meaning a well-crafted system message can override default model behaviors and establish new conventions for a particular deployment.

A system message might specify:

This tells the model how to behave across the entire conversation. Every response should be concise, should cite sources, and should acknowledge uncertainty. These constraints persist regardless of what the user asks. If the user later asks for a long, detailed explanation, the model must balance that request against the system instruction for conciseness. Through training on examples that contain similar tensions between system and user instructions, the model learns to resolve these situations, typically by honoring system constraints while still being as responsive as possible to user requests.

System messages became prominent with ChatGPT and similar conversational AI systems. They allow the same base model to behave differently in different contexts without any additional fine-tuning. A customer service application might use a system prompt stressing politeness and company policy, while a coding assistant might use one stressing technical accuracy and code quality. A creative writing assistant might receive a system prompt encouraging imagination and stylistic flourish. A medical information assistant might use a system prompt reminding the model to always recommend consulting a healthcare professional. This flexibility means a single trained model can power many different applications, each with its own personality and constraints, sharply reducing the cost and complexity of deploying specialized AI systems.

The depth of behavioral control that system messages give depends heavily on how much system-message diversity was included in the training data. A model trained almost entirely on a single system prompt will have learned to follow that one prompt expertly but may respond unpredictably to novel system prompts at inference time. Models trained on system prompts with varied writing styles and constraints generalize much better. This is why datasets like OpenAssistant and Dolly deliberately varied their system prompts, and why commercial models are typically trained on enormous pools of human-written system prompts.

The positioning of system messages matters for how the model processes them. Most formats place the system message at the very beginning of the conversation, before any user turns. This ensures the model processes instructions before encountering user requests, letting those instructions to condition all subsequent attention computations. Some formats allow system messages to appear mid-conversation, but this is less common and can confuse models not trained to expect it. The model has learned that system messages come first and set the stage; encountering one mid-conversation violates that learned pattern and may produce inconsistent behavior.

During training, system messages are typically included in the input but excluded from the loss calculation. The model sees the system message and learns to condition its responses on it, but it is not penalized for failing to predict the system message tokens themselves. This makes sense: we do not want the model to learn to generate system messages; we want it to learn to follow them. The asymmetry in how loss is applied creates an asymmetry in what the model learns to do: it becomes expert at being conditioned by system messages, not at creating them.

Writing effective system messages is both a science and an art. The model responds to system instructions because it has seen thousands of training examples where similar system instructions preceded certain kinds of behavior. The closer your system message is to the kinds of instructions the model saw during training, the more reliably it will follow them. Vague instructions like "be helpful" work poorly because helpfulness is already the default; the system message adds no specificity. Precise instructions like "always structure your response with a brief summary followed by numbered steps" work much better because they give the model a concrete behavioral pattern to match.

Some practitioners decompose complex behavioral requirements into multiple distinct instructions within a single system message, covering tone, format, knowledge boundaries, and persona separately. Others find that very long system messages exceed what the model can reliably attend to across a long conversation, since early tokens in a long context receive less attention weight than recent tokens. Finding the right balance between completeness and conciseness in system messages is an empirical question that depends on the model and the application.