Configuration

MUTX uses XDG-style paths by default.

Paths

• Config directory: ~/.config/mutx/
• Data directory: ~/.local/share/mutx/
• Bootstrap file: ~/.config/mutx/config.toml
• Default socket path: /tmp/mutx/mutx.sock

After first run, most settings live in the SQLite database under the data directory. The TOML file becomes a minimal bootstrap file, mainly for db_path.

CLI and environment overrides

mutx supports these overrides:

• --config-dir or MUTX_CONFIG_DIR
• --data-dir or MUTX_DATA_DIR
• --socket-path or MUTX_SOCKET_PATH
• --log-file or MUTX_LOG_FILE
• --log-level or MUTX_LOG_LEVEL

Bootstrap example

db_path = "/home/alice/.local/share/mutx/mutx.db"

Runtime settings

The application persists settings such as:

• theme flavor: mocha, latte, macchiato, frappe
• log level
• log-to-file toggle
• vim navigation mode
• hidden balance mode
• dashboard animation toggle
• Solana network default
• explorer URL templates for Solana
• keybindings

Per-wallet custom RPC

By default, every wallet routes through the managed MUTX RPC proxy (https://<network>.<blockchain>.rpc.mutx.net). You do not need to configure anything for this to work.

If you want a wallet to use your own RPC endpoint (a private Helius URL, an internal validator, Alchemy, Infura, etc.), open the wallet details page and set the custom RPC URL field for that single wallet. Other wallets are unaffected.

There is no global “override the RPC for every wallet on chain X” setting — this is per wallet by design.

Auto-refresh

Balances and token lists refresh in the background every 30 seconds. You do not need to configure this. The TUI’s b key still triggers an immediate manual refresh.

Explorer URL overrides (Solana)

You can override the explorer URL templates that the TUI uses for transactions and addresses on Solana. Useful if you prefer Solana Beach, Solscan, or your own explorer over the default.

Templates use {tx} for transaction signatures and {addr} for addresses, configurable per cluster (devnet / testnet / mainnet).