Configuration

PromptDeploy is configured through a combination of settings in the web UI and an optional YAML config file in your repository. You can configure prompts entirely through the UI, entirely through the config file, or a mix of both.

`.promptdeploy.yml` (optional)

Add a config file to your repository root to define managed prompts in version control. This is useful for teams who want prompt definitions to live alongside code, but it's not required — you can always add prompts manually through the UI.

prompts:
  - path: prompts/system.txt
    name: System Prompt
    deploy_mode: pr
    provider: anthropic
    model: claude-sonnet-4-20250514

See the full .promptdeploy.yml reference.

Key concepts

Deploy modes

Each prompt can deploy changes in one of two ways:

Direct — commits changes straight to the default branch
PR — creates a pull request for code review before merging

See Deploy Modes.

Variables

Prompts can define template variables as metadata. These help document the expected inputs for your prompt templates.

See Variables.

Syncing configuration

When you update .promptdeploy.yml in your repository, you can sync the changes by clicking Sync config on the repository page. This re-reads the config file and updates prompt definitions to match.