Configuration & data
Where Harmony keeps its files, the environment variables that matter, and the config CLI.
Where things live
| What | Windows | Linux / macOS |
|---|---|---|
| App install | %LOCALAPPDATA%\NALA\ | /opt/nala/ (DEB/RPM) or AppImage |
| User data (sessions, tasks, scrollback) | %APPDATA%\wmux\ | ~/.config/wmux/ |
| Logs | %APPDATA%\wmux\logs\ | ~/.config/wmux/logs/ |
| CLI shim | %LOCALAPPDATA%\NALA\bin\ | /usr/bin/ (DEB/RPM) or ~/.local/bin/ |
The internal data identity stays wmux (the upstream project nala descends from) for stable paths and single-instance compatibility. Do not rename it without a migration plan.
The config CLI
nala config get [key] # one key, or everything
nala config set <key> <value>
nala config unset <key>
nala config path # where the file lives
nala config validate # check it parses
Project and workspace behavior can also be shaped per-repo with a wmux.json file (trust-gated before it is honored).
Environment variables
| Variable | Default | Purpose |
|---|---|---|
NALA_WHISPER_MODEL | small | Whisper model for dictation (tiny … large-v3) |
NALA_WHISPER_PYTHON | python / python3 | Python executable for the voice worker |
NALA_WHISPER_PRELOAD | on | Warm the model after app start; 0 to skip |
NALA_NO_BANNER | unset | Set 1 to suppress the TUI launch banner |
KIMI_SHELL_PATH | unset | Git Bash path for Kimi Code on Windows |
Per-repo and per-user secrets (provider API keys, tokens, model weight caches) belong to the providers' own config homes. Never commit .env files or credential material to a repo.
Data lifecycle facts worth knowing
- Suspended sessions persist 7 days, then expire.
- Channel history caps at 5,000 messages per channel; empty channels are reaped after 7 days.
- Update-migration backups (
migration-backup-{timestamp}/) are retained for 7 days. - Reset All Data (Settings → Recovery, or the safe-mode recovery panel) clears local data only, behind a double confirmation (type
NALA). There is no product subscription to cancel; manage third-party agent accounts with their providers.
Diagnostics
nala doctor checks the daemon, Node runtime (including the managed portable runtime Harmony can install under user data), provider probes, MCP registration, voice models, and signing state. --json for machines, --fix-safe to repair the safe class of findings automatically. Logs for everything the daemon does are in the logs directory above.