Install & update
Get Nox.
Or update it.
Install a release binary, build from source with Cargo, or bring an existing installation forward with Nox's built-in updater.
Release artifacts
Choose the binary that matches your platform and architecture. Release assets are served directly from GitHub.
Put a release on your PATH.
After downloading an executable asset, rename it to nox if needed and install it into a user-owned bin directory.
mkdir -p "$HOME/.local/bin"
chmod +x ./nox
install -m 755 ./nox "$HOME/.local/bin/nox"
export PATH="$HOME/.local/bin:$PATH"
nox versionAdd the PATH export to your shell profile to keep it available in new terminals. A system-wide installation may use /usr/local/bin instead, when you have permission to write there.
Install with Cargo.
This follows the same Git-based installation model used by nox update. It requires Rust and Cargo on your PATH.
cargo install --git https://github.com/playfairs/nox.git nox --locked
nox version
nox helpFor a checkout you are actively developing, use cargo build --release first, then run ./target/release/nox install --release from the project root.
Let Nox update itself.
The updater checks the stable channel by default, compares semantic versions, and uses Cargo to replace the installed executable. It never automatically downgrades.
Stable
nox updateDevelopment
nox update --devExact version
nox update --version 1.2.3Nix-managed installations are intentionally different: run nix flake update nox from the directory containing your Nix configuration, then rebuild through your normal Nix workflow.
Confirm the executable you are using.
Use these after an install or update, especially when more than one Nox binary may be on your PATH.
command -v nox
nox version
nox help update