TLDR:
ahvn setup is all you need.ahvn config subcommand (aliased ahvn cfg), using dot-separated key paths like llm.providers.openrouter.api_key.
1. Initialization
Runahvn setup once after installation to initialize the ahvn under user home (~/.ahvn/) and create the default config files.
--reset will overwrite existing configuration files and clean up any existing data. Use with caution.
2. Config Inspection
ahvn config show (aliased ahvn cfg show or ahvn cfg ls) prints the full merged config as YAML. Pass a dot-separated key path to inspect a specific value:
3. Config Editing
ahvn config set writes a single value. Values are auto-typed — booleans, integers, and strings are inferred automatically:
ahvn config unset (aliased ahvn cfg unset, ahvn cfg rm or ahvn cfg del) removes a key from the current config (which is different from setting it to null or an empty string). Unsetting a key causes it to fall back to the default value if available:
4. Edit Config in Editor
For bulk edits,ahvn config edit opens the current config in the system editor (env $EDITOR) as a temporary YAML file. Changes are written back to the database on save:
On Windows with no
$EDITOR set, notepad opens. On macOS and Linux, nano is likely the fallback.
