Help
Deployment Settings
What the Deployment Settings editor configures, field by field, and what Deploy does with it.
Deployment Settings shape how a persona will be delivered to one target agent runtime environment. Together with the Communication Style set points, they form the persona’s working configuration — one editable draft you can adjust at any time, even after the persona is locked. Deploying a persona commits that configuration as the target’s Deployment (one per target) and freezes its Persona Kit files at every detail level overwriting any prior deployments to the same target environment.
The fields
| Field | What it sets |
|---|---|
| Target Runtime Environment | The runtime environment that the persona will be deployed to. The Persona Kit of configuration files used for deployment will be written for this environment. |
| Deployment name | Your own label for this configuration. |
| Deployment notes | Your notes about this configuration. These are for you; they do not change the configuration files. |
| Prompt Detail Level | How much room the persona’s core instructions take. Deploy freezes a Persona Kit at every level, so this choice only picks which one you download first. |
| Deployment Details | This section includes optional details that may be used in some environments - the persona’s role, who it serves, anti-sycophancy, and personality integrity. For example, “creature type” is unique to Open Claw. |
| Deployment Add-ons | Optional inserts appended to the prompt configuration text for specific capabilities. |
Changing the working configuration after a Deploy does not touch the committed Deployment — its files stay frozen exactly as deployed until you deploy that target again.