Where Is the Himalaya Config File?
Himalaya reads config.toml from the himalaya folder under XDG config home. The wizard can generate it from your email address.
Last updated
Himalaya loads one TOML file from the first valid path in a short lookup order: XDG config home, then home config, then a dotfile fallback. The same file backs both the CLI and the TUI, with each side ignoring the other's keys.
The sample config in the repo is the documented template. Passwords deserve care: prefer the command or keyring auth options over raw secrets in the file. Attachment downloads default under Downloads unless a per call directory is given. Never store passwords raw in the file when a keyring or command option exists.
Where Himalaya stores this, by platform
/home/<username>/.config/himalaya/config.toml
Main config with accounts and backends. Copy config.sample.toml here to start by hand.
/Users/<username>/.config/himalaya/config.toml
Same lookup order on Mac. The wizard writes this path when it discovers your provider.
Frequently asked questions
How do I add an email account?
Run the bare himalaya command with no config present. It probes autoconfiguration and writes the account to disk. Merge the printed TOML into your file.
Can I keep configs per machine?
Pass a custom path with the config flag. Multiple colon separated paths deep merge, with the first as the base. One file backs both CLI and TUI.
Notice an outdated path? Let us know.