Runtime config vs workflow YAML
Use this page when you are in the workflow docs and need the fast boundary:
- If you are defining what the pipeline does, stay in
.loom/workflow.yml. - If you are setting local runtime defaults or inspecting the merged runtime config, go to Runtime config.
Runtime config is runtime-only. It is not a second workflow language.
Use the right surface
| Surface | Use it for |
|---|---|
.loom/workflow.yml | Jobs, stages, scripts, cache, variables, and workflow secret references |
.loom/config.yml | Repo-scoped runtime defaults for local execution |
~/.config/loom/config.yml | User-scoped runtime defaults on one machine |
| Environment variables | Secret values and one-off runtime overrides |
.loom/workflow.yml remains the executable workflow source of truth.
What runtime config affects today
The current runtime config surface is consumed only by:
loom config showloom run --local
loom check and loom compile do not read layered runtime config.
What belongs in runtime config
Runtime config is the right place for:
- a default Docker workspace mount mode
- KeePass alias defaults that map onto
LOOM_KEEPASS_DB_* - the env var name that should supply the 1Password service account token
Runtime config is not the place for:
- jobs, stages, or scripts
- workflow variables or cache rules
- workflow secret references
Continue in the config section
The config section covers the runtime-only details: