System Prompt Modes
Define how custom prompts interact with the system prompt.
When customizing system prompts in Msty Studio (ie, with Projects and Personas), you can control how your custom instructions are combined with the default system prompt using three modes:
- Prepend
- Replace
- Append
Each mode affects how the model interprets behavior and tone. Below are examples and explanations for each mode, along with their advantages and disadvantages. The examples use the following prompts:
Prepend
Definition: Your custom prompt is added before the system prompt.
Example:
Advantages:
- Gives your custom instructions priority.
- Useful for setting tone, style, or specific roles early on.
- Keeps the base safety and helpfulness rules.
Disadvantages:
- May conflict with the system prompt if the tones differ.
- Custom behavior may not fully override the assistant’s defaults.
Best For: When you want to strongly guide behavior or persona, but still retain the assistant’s helpful baseline.
Replace
Definition: Your custom prompt completely overrides the system prompt.
Example:
Advantages:
- Gives you full control of the assistant’s behavior.
- Ideal for custom personas, creative characters, or specialized workflows.
Disadvantages:
- Removes all behavior (e.g., safety, neutrality, helpfulness).
- Requires careful crafting to avoid issues or undesired responses.
Best For: When you want to define the assistant’s role or tone entirely from scratch.
Append
Definition: Your custom prompt is added after the system prompt.
Example:
Advantages:
- Preserves the default assistant behavior.
- Great for subtle additions, like tone adjustments or specific response styles.
- Less likely to conflict with system rules.
Disadvantages:
- Lower priority — your custom instructions may be overridden or ignored.
- Not ideal for dramatic behavior shifts.
Best For: When you want to enhance or refine the assistant’s responses, without changing its core behavior.
Comparison Table
| Mode | Behavior | Conflict Risk | Control Level | Keeps System Prompt |
|---|---|---|---|---|
| Prepend | Adds your prompt before system | Medium | Medium | ✅ Yes |
| Replace | Uses only your prompt | Low | High | ❌ No |
| Append | Adds your prompt after system | Low | Low–Medium | ✅ Yes |
Project Hierarchy
For project hierarchy, ie. a project folder that has child and grandchild project folders, can leverage prepend and append system prompt modes to create a chain of prompts.
The default is to replace any inherited system prompts. Meaning, a child project will ignore a parent's system prompt by default unless you choose to prepend or append the child's system prompt to it's parent's system prompts.
For example: A parent project folder has a system prompt "I'm the parent." A child (nested) project under the above parent has a system prompt "I'm the child."
In the child's project settings, if System Prompt Attach Mode is set to:
- Replace (default), then a new convo will have a system prompt of "I'm the child."
- Prepend, then a new convo will have a system prompt of "I'm the child. I'm the parent."
- Append, then a new convo will have a system prompt of "I'm the parent. I'm the child."