The two quickest routes are in the README: Homebrew and the install script. Every other supported route is here.
| Tool | What it powers | Comes with |
|---|---|---|
| tmux 3.1+ | every agent session | Homebrew, AUR, install script |
| git | diff review and worktree sessions | Homebrew (git runs Homebrew itself), AUR, install script |
| wl-clipboard, xclip, or xsel | pasting images into a prompt on Linux | your package manager |
| notify-send | desktop notifications on Linux | your desktop's notification package |
The mise, go install, and prebuilt-binary routes install the binary alone, so install tmux and git with your package manager. When the manager starts without tmux, or the diff view cannot find git, it names the install command it detected, or tells you to use your package manager.
brew install --cask yoanwai/tap/agent-managerInstalls the released binary rather than building it, and pulls in tmux. The README covers brew install agent-manager, the homebrew-core formula that builds from source.
yay -S agent-manager-bin
agent-manager-bin in the AUR installs the released binary and pulls in tmux and git.
mise use -g ubi:YoanWai/agent-managerReads the GitHub release directly, so it needs no registry entry. Install tmux and git with your own package manager.
go install github.com/YoanWai/agent-manager@latestRequires Go 1.27.1+, tmux 3.1+, and git; installs to $(go env GOPATH)/bin.
Download from Releases (macOS and Linux, amd64/arm64), and install tmux and git with your package manager.
Run inside WSL2: agent-manager lives on tmux, which is a Linux/macOS tool. In a WSL shell, install with the install script, with Homebrew, or grab the Linux binary from Releases.
The agent CLIs belong in the distro too. WSL appends the Windows PATH to the distro's, so a CLI installed on the Windows side is visible in a WSL shell, and running it there starts a Windows process or fails for want of a Linux runtime. A spawn finding only that copy stops on the setup dialog, which names where the Windows copy is and the command that installs the CLI in the distro.
The manager checks GitHub Releases every ten minutes and shows a ↑ vX.Y.Z available badge in the header when a newer version is out. Press u on the update message (or enter on the version row in Settings) and what happens next follows the install. A Homebrew, mise, or AUR install hands the terminal to that package manager's own upgrade command, so its progress and any password prompt behave as they would in a shell. An install-script, go install, or manual download is updated in place, by downloading the release and swapping the binary. Either way the manager restarts into the new build with every session still running.
Two cases update by hand. A pacman-owned install needs an AUR helper (yay or paru) on PATH, and without one the manager runs nothing and prints the command to use instead: yay -S agent-manager-bin. A Nix install lives in the read-only store, so the manager runs nothing and points you at Nix instead, such as nix profile upgrade agent-manager or your flake or NixOS config.
The same commands work from a shell:
brew upgrade agent-manager # Homebrew formula
brew upgrade --cask yoanwai/tap/agent-manager # Homebrew cask
curl -fsSL https://raw.githubusercontent.com/YoanWai/agent-manager/main/install.sh | sh # Install script
mise upgrade --bump ubi:YoanWai/agent-manager # mise
go install github.com/YoanWai/agent-manager@latest # GoLater, agent-manager update brings the binary to the newest release without re-running any of these: it hands the update to the package manager that installed it, or downloads and swaps the binary itself.