cwp config set

cwp config set <key> <value> [flags]

Local only — it acts on no environment.

Argument	What it is	Default
<key>	dotted path, e.g. pull.uploads
<value>	new value; a comma-separated list for list keys

Plus the shared flags --json, --verbose and --dry-run.

What it does

Writes one key to whichever layer owns it — .cwp.yml for project keys, ~/.config/cwp/config.yml for machine keys.

Example

cwp config set pull.uploads sync
cwp config set defaults.uploads sync
cwp config set pull.keep_roles administrator,editor
cwp config set pull.uploads sync --dry-run

What it does not do

It does not pin defaults into your file. It writes back your file with one key changed, never a serialised copy of the parsed config — otherwise every schema default would be frozen into the file the first time you set anything, and a default cwp later corrects would never reach you.

It touches nothing else in the file. The YAML document is edited in place rather than re-serialised, so your comments, key order and formatting survive and a one-key change is a one-line diff. It used to strip every comment (B-030).

It deletes no keys, creates no environments and contacts nothing.