FAQ

What shells are supported?

Shell	Status
Fish	Fully supported and tested
PowerShell	Supported and tested (5.1 + 7)
Zsh	Supported, not yet tested
Bash	Supported (3.2+)
Brush	Supported (bash-compatible)
Nushell	Not yet implemented

How is this different from shell aliases in my dotfiles?

Traditional aliases are static — defined once in your .bashrc or .zshrc. amoxide adds:

• Profiles — named groups you can activate/deactivate without editing files
• Project aliases — auto-loaded per directory, like direnv for aliases
• Parameterized aliases — template syntax for composable commands
• Multiple active profiles — layer aliases with clear precedence

Where are my aliases stored?

• Global aliases: ~/.config/amoxide/config.toml
• Profile aliases: ~/.config/amoxide/profiles.toml
• Project aliases: .aliases file in the project directory

Can I use amoxide alongside my existing shell aliases?

Yes. amoxide aliases coexist with your shell's native aliases. If there's a name conflict, amoxide's alias takes precedence while it's active.

What is am-tui?

A separate binary (amoxide-tui) that provides an interactive terminal UI for managing aliases visually. Once installed, it integrates directly into am:

am tui

The am tui command launches the TUI — no need to remember a separate binary name. Quick install:

brew install sassman/tap/amoxide-tui

See all installation options for Shell Script, PowerShell, and Cargo.

I changed my config file manually — how do I apply the changes without restarting my shell?

Run am init -f <shell> to reinitialise in place. This unloads all current aliases and reloads everything from your config, including any setting changes like use_abbr = true in Fish. See Reinitialising Without Restarting for full details.

Fish

am init -f fish | source

Zsh

eval "$(am init -f zsh)"

PowerShell

(am init -f powershell) -join "`n" | Invoke-Expression

Bash

eval "$(am init -f bash)"