Config keys
Read or write the non-secret CLI config (preferences + routing defaults).
The config never holds secrets: seeds live in identity.json, relay credentials in relay.json. A secret-looking key (…key/…token/…seed…) is refused. Honors $TALLY_HOME.
The ui_* and watch_* keys tune tally ui and are read at its startup. api_url/relay_url are routing DEFAULTS for every endpoint resolution (precedence: flag > env > config > embedded > built-in); they do not rewrite an existing relay.json: re-run tally connect for that.
The --help text is the full extent of what the binary documents per key; read and write them with tally config:
tally config get default_harness
tally config set default_harness pi