Policies

Named run presets and how they merge with CLI flags and form YAML.

Related: concepts · commands/run · commands/policies · repeat

List forms (optional live flags)

gform list
gform ls
gform list --policy          # also fetch live risk flags
gform list --policy --json

Output includes steps, pools, history counts. --policy on list means “fetch live risk flags” — not the same as run --policy.

Named run policies

gform policies
gform pol
gform policies --json

gform run <form> --policy safe
gform run <form> --policy demo
gform run <form> --policy load
gform run <form> --policy watch

Policy	Defaults (from core)
safe	1× headless; --once; --skip-duplicates; --strict; variantMode: rotate
demo	1× headed; soft walls can assist on TTY
load	10× headless; concurrency 5; skip-duplicates; continue-on-error; rotate
watch	1× headed + keep-open

Policies set how the run behaves. They do not rewrite step answers.

Precedence

Highest wins:

1. Explicit CLI flags you actually passed
2. Named --policy / -P
3. Form YAML options starters (headed, repeat, …)
4. Engine defaults

gform run <form> --policy load --repeat 3 --concurrency 2

Run intro prints provenance for headed / repeat / concurrency so the merge is visible.

Choosing a policy

Goal	Start with
Watch + assist	demo or watch
Single careful submit	safe
Parallel varied repeats	load + step pools
Custom	omit --policy and pass flags

Max workers: 16 (capped; also capped at --repeat).