Set your preferences with tovio config
Turning off hints, celebration lines and git-compat notes, and the keys worth knowing.
Written By Dustin
Last updated About 3 hours ago
tovio config listtovio config get <key>tovio config set <key> <value>tovio config unset <key>Reads and writes this repository's preferences, stored as plain key = value lines in .tovio/config. unset removes a key, reverting it to its default.
One caveat if you edit the file by hand: the reader ignores # comments and blank lines, but the writer does not preserve them. Every config set and config unset rewrites the whole file from the parsed keys, sorted, as bare key = value lines — so a comment you added is silently dropped by the next write. Keep the reasoning in your team docs, not in the file.
Keys worth knowing
An unrecognised value is generally treated as “not off” rather than as an error, so a typo leaves the default in place instead of silently disabling something.
Credentials never go here
The config file is plain text in the repository directory, so provider credentials are refused outright: ai.api_key, ai.openai.api_key, ai.token and ai.credential_value are rejected with TVO-CLI-024 (exit 2) without echoing the value. Use the sealed local keystore instead:
<secret-manager> | tovio config secret set <reference> --from-stdintovio config set ai.credential <reference>The secret bytes go to the OS-keychain-wrapped keystore; only the reference is written to config. See the AI collection for the full flow.
Scope
These preferences are per repository — there is no global user file, and .tovio/config is never synced. Environment overrides exist for the CI case, where you want the quiet behaviour without committing a preference.
Where to find it
config is Advanced-tier, so it is hidden from the default tovio help index. tovio help --all lists it, and tovio help config prints its full help regardless of tier.