| description | Install mise on macOS, Linux, or Windows and connect it to your shell. |
|---|
If you are new to mise, follow the Getting Started guide first.
Choose one installation method, verify the executable, then configure your shell if you want automatic project activation. Use the same package manager for future updates when it owns your mise installation.
| Platform | Recommended | Alternative |
|---|---|---|
| macOS | mise.run | Homebrew |
| Linux | mise.run | System packages |
| Windows | Scoop | winget |
| Any (Rust users) | cargo binstall | cargo install |
| CI/Docker | mise.run | GitHub Releases |
The official single-binary release installed by mise.run is the preferred method on macOS and
Linux. These binaries are built with mise's optimized release profile and can be updated immediately
with mise self-update. Prefer them over third-party package builds: the Homebrew formula can be
substantially slower and larger, and package-manager releases may also trail a mise release.
::: tip Which methods auto-update?
Package managers (apt, dnf, brew, pacman, etc.) update mise when you update system packages. Official standalone installations support mise self-update; a build or
package may disable it. Updating mise itself is separate from mise upgrade,
which updates managed tools.
For installations that support mise self-update, automatic updates can be enabled globally:
mise settings auto_update=truemise then periodically checks before eligible interactive commands, installs a newer release without
updating plugins, and re-runs the original command with the new binary. Configure the interval with
auto_update_check_duration.
For releases from v2026.9.3 onward, self-update also verifies the release's packslip: its signed archive digest, version, release workflow, and transparency-log entry. The signer is pinned to mise's immutable GitHub repository ID, so repository renames and moves between organizations do not change which project is trusted. The minimum release age also applies to the verified log timestamp; explicit versions bypass the delay. Older releases retain the embedded archive-signature check, which is also required for newer releases. Mirrors must preserve the original manifest and archive bytes. Missing or invalid manifests for modern releases fail the update without replacing mise.
Organizations can direct manual and automatic self-updates to a curated GitHub release mirror by
setting self_update.repository. Private
repositories and GitHub Enterprise use mise's existing GitHub token resolution. Mirrored archives
must retain the official file names and embedded mise signatures. The API URL must use HTTPS:
[settings.self_update]
repository = "myorg/mise-mirror"
api_url = "https://api.github.com"These settings are global-only: set them in the user-global or system configuration, not a project configuration. :::
::: tip Keep mise up to date mise connects to many external registries and backends, such as aqua, GitHub releases, language package registries, and system package managers. Those services change over time, so mise works best when the CLI is kept on a recent version.
Projects and organizations should generally set a min_version when they need a newer mise feature instead of locking every user to a specific mise executable. While there are ways to pin or bootstrap a particular mise version, locking users to one mise version is generally discouraged. A fixed mise version can be useful in controlled CI builds, but it needs a
planned update process as upstream registries evolve. min_version lets a
project require a feature while allowing users to keep their CLI current.
:::
mise does not need to be on PATH. If you run the activate script in your shell's rc file,
mise adds itself to PATH automatically.
curl -fsSL https://mise.run | shTo choose another executable path (its parent must be writable by your user):
curl -fsSL https://mise.run | MISE_INSTALL_PATH="$HOME/bin/mise" shFor a more streamlined setup, use the shell-specific endpoints, which install mise and configure activation in your shell's configuration file:
::: code-group
curl -fsSL https://mise.run/zsh | sh
# Installs mise and adds activation to ~/.zshrccurl -fsSL https://mise.run/bash | sh
# Installs mise and adds activation to ~/.bashrccurl -fsSL https://mise.run/fish | sh
# Installs mise and adds activation to ~/.config/fish/config.fish:::
These shell-specific installers will:
- Install mise using the same logic as the main installer
- Append activation to the selected shell's configuration (
ZDOTDIRis honored for zsh; fish uses~/.config/fish/config.fish) - Skip that append when the same shell installer's marker is already present
If activation was added manually or by a package manager, inspect the file first: the installer marker check does not detect every equivalent hook.
Options:
MISE_DEBUG=1– enable debug loggingMISE_QUIET=1– disable non-error outputMISE_INSTALL_PATH=/some/path– change the binary path (default:~/.local/bin/mise)MISE_VERSION=v2025.12.0– install a specific version, bypassing the release-age delayMISE_SELF_UPDATE_MINIMUM_RELEASE_AGE=7d– override the minimum age for mise releases; falls back toMISE_MINIMUM_RELEASE_AGE, then24h. Use0sfor immediate releases. The installer supports integers,m,h,d, andwdurations and reads environment variables, not TOML settings.MISE_INSTALL_SKIP_IF_EXISTS=1– skip the download/install if the mise binary at the install path already matches the requested versionMISE_INSTALL_MUSL=1– use the static musl build on systems with older glibc
To verify the install script hasn't been tampered with:
gpg --keyserver hkps://keys.openpgp.org --recv-keys 24853EC9F655CE80B48E6C3A8B81C9D17413A06D
curl -fsSL -o install.sh.sig https://mise.jdx.dev/install.sh.sig
gpg --output install.sh --decrypt install.sh.sigConfirm that GPG reports a valid signature by the release key with fingerprint
24853EC9F655CE80B48E6C3A8B81C9D17413A06D. If download or verification fails,
stop; do not run the output. After successful verification:
sh ./install.sh::: tip
The installer selects the newest stable release published at least 24 hours ago. It evaluates
release ages when run, even if you saved the script earlier. Set MISE_VERSION to pin a version
for reproducible installs. Unpinned installs keep an existing version if it is already as new as
or newer than the eligible release.
curl -fsSL https://mise.run | MISE_SELF_UPDATE_MINIMUM_RELEASE_AGE=7d shFor subsequent updates, mise self-update uses [settings].self_update.minimum_release_age,
falling back to [settings].minimum_release_age and then 24h. Its
--minimum-release-age flag overrides both settings, and an explicit version bypasses the delay.
Automatic updates and update notifications use the same cutoff.
:::
Supported OS/arch:
macos-x64macos-arm64linux-x64linux-x64-musllinux-arm64linux-arm64-musllinux-armv7linux-armv7-musl
The linux-x64, linux-arm64, and linux-armv7 builds are dynamically linked and
require glibc 2.18 or newer. For systems with older glibc or a different
libc, such as musl on Alpine Linux, use the matching static -musl build. These
builds do not require glibc.
The installer at mise.run selects musl builds automatically on musl systems.
On glibc systems, it selects a GNU build without checking the glibc version. If
your glibc is older than 2.18, select the musl build explicitly:
curl -fsSL https://mise.run | MISE_INSTALL_MUSL=1 sh::: details Policy for raising the glibc minimum
Before mise raises its glibc minimum, every distribution with an older version must have reached the end of standard vendor support. Extended-support programs, such as Ubuntu ESM, RHEL ELS, and SUSE LTSS, do not extend this period. Users of those systems can use static musl builds.
The following table lists standard support end dates for several distributions:
| glibc | Distros | Standard support ends |
|---|---|---|
| ≤ 2.27 | RHEL 7, Ubuntu 16.04 / 18.04, Debian 9, Amazon Linux 2 | ended (last: Amazon Linux 2, 2026-06-30) |
| 2.28 | Debian 10 | ended 2024-06-30 |
| 2.28 | RHEL 8, Rocky 8, AlmaLinux 8 | 2029-05-31 |
| 2.31 | Ubuntu 20.04, Debian 11 | ended (last: Debian 11, 2026-08-31) |
| 2.34 | Amazon Linux 2023 | 2029-06-30 |
| 2.34 | RHEL 9, Rocky 9, AlmaLinux 9 | 2032-05-31 |
| 2.35 | Ubuntu 22.04 | 2027-06-01 |
The minimum remains glibc 2.18. These dates inform future compatibility changes; they do not set a release schedule. The same support policy applies to distributions omitted from the table.
:::
If you need something else, compile it with cargo install mise (see below).
For Alpine Linux:
apk add misemise lives in the community repository.
::: warning Alpine source-build default is deprecated
Alpine currently compiles tools from source by default. This automatic behavior is deprecated:
affected source installs warn beginning in mise 2026.8.0, and the default will switch to
precompiled binaries in mise 2027.8.0. To keep compiling from source, set
all_compile = true explicitly.
:::
On Ubuntu 26.04+, mise is available via a PPA:
sudo add-apt-repository -y ppa:jdxcode/mise
sudo apt update
sudo apt install -y miseOn Debian 11+ and Ubuntu 22.04+, the mise repository can be enabled with extrepo:
sudo apt install -y extrepo
sudo extrepo enable mise
sudo apt update
sudo apt install -y miseFor Arch Linux:
sudo pacman -S miseSource builds need a Rust toolchain meeting the selected release's
rust-version and the platform's compiler and native library prerequisites.
See contributing for the build dependencies. Build with Cargo:
cargo install --locked miseDo it faster with cargo-binstall:
cargo install --locked cargo-binstall
cargo binstall miseBuild from the latest commit on main:
cargo install --locked mise --git https://github.com/jdx/mise --branch mainsudo dnf copr enable jdxcode/mise
sudo dnf install miseRHEL 9 AppStream is currently frozen at Rust 1.88, which is older than mise's minimum supported Rust version. Use the CentOS Stream 9 build instead — the resulting binary works on RHEL 9 derivatives:
sudo dnf copr enable jdxcode/mise centos-stream+epel-next-9
sudo dnf install misesudo snap install mise --classicOfficial images are available from ghcr.io/jdx/mise and Docker Hub (jdxcode/mise)
for Linux amd64 and arm64:
- Use
ghcr.io/jdx/mise:2026.9.11-debianas a CI or development image. It includes mise,curl,git, and CA certificates; install project tools withmise install. - Use
ghcr.io/jdx/mise:2026.9.11as aCOPY --from=source for the static mise binary at/usr/local/bin/mise. This scratch image has no shell.
See the Docker cookbook for tags, digest pinning, migration from the previous image, and other installation methods.
::: details Example Dockerfile
Put a mise.toml declaring node = "24" under [tools] in the Docker build
context. This example copies that configuration, installs its tools, and uses
mise exec for the container command. Add any other configuration files,
lockfile, hook inputs, or application files that your real project needs.
FROM ghcr.io/jdx/mise:2026.9.11-debian
WORKDIR /app
COPY mise.toml ./mise.toml
RUN mise trust && mise install
ENTRYPOINT ["mise", "exec", "--"]
CMD ["node", "--version"]:::
::: warning
The Homebrew formula is convenient, but it is not the preferred installation method. Homebrew builds
mise separately from the official, more optimized release binaries. For the best performance and
fastest access to new releases, use the mise.run installer instead.
:::
brew install misemise is available on npm as a precompiled binary. It isn't a Node.js package—it is only distributed
via npm. This is useful for JS projects that want to set up mise via package.json or npx.
npm install -g miseUse npx to run mise without adding it as a permanent global npm package. npm caches its download, and any tools mise installs remain in mise's data directory:
npx --yes mise exec [email protected] -- python --versionThe legacy @jdxcode/mise package is still published.
Choose a version and the matching OS/architecture artifact from GitHub Releases. For example, to download a Linux x64 executable to a temporary working directory:
mise_version=2026.9.1
mise_platform=linux-x64
curl -fL -o mise "https://github.com/jdx/mise/releases/download/v${mise_version}/mise-v${mise_version}-${mise_platform}"Change both values for your chosen release and platform. Each release also
ships SHASUMS256.txt, signed with minisign (SHASUMS256.txt.minisig) and
GPG (SHASUMS256.asc). Verify the checksum file's signature, then the
download against it, before installing. The following commands require
minisign and sha256sum (use shasum -a 256 -c on macOS in place of
sha256sum -c), and reuse the variables and mise file from the download above:
base="https://github.com/jdx/mise/releases/download/v${mise_version}"
curl -fL -O "$base/SHASUMS256.txt" -O "$base/SHASUMS256.txt.minisig"
minisign -Vm SHASUMS256.txt -P RWTC3g8W3z4RZK3V3qv7fa1QY4JEWyBtqIHW+85QlJpZc5yG+uNYNBSZ &&
grep " ./mise-v${mise_version}-${mise_platform}$" SHASUMS256.txt | sed 's| ./mise-.*| mise|' | sha256sum -cThe minisign public key is
minisign.pub in the
repository. The mise.run installer handles platform selection and checksum
checking for you.
After verifying a downloaded Unix executable, install it to a user-writable path:
mkdir -p ~/.local/bin
install -m 755 ./mise ~/.local/bin/mise
~/.local/bin/mise --versionsudo port install miseFor the Nix package manager, at release 24.05 or later:
nix-env -iA nixpkgs.miseTo try the Nixpkgs package without a persistent installation, run
nix-shell -p mise --run "mise --version".
This repository also exposes a flake package at
inputs.mise.packages.${system}.mise when your flake declares a mise input
pointing to github:jdx/mise. The attribute is a Nix expression, not a shell command.
::: warning NixOS source-build default is deprecated
NixOS currently compiles tools from source by default. This automatic behavior is deprecated:
affected source installs warn beginning in mise 2026.8.0, and the default will switch to
precompiled binaries in mise 2027.8.0. Enable nix-ld before that
change. To keep compiling from source, set
all_compile = true explicitly.
:::
sudo yum install -y yum-utils
sudo yum-config-manager --add-repo https://mise.jdx.dev/rpm/mise.repo
sudo yum install -y misesudo wget https://mise.jdx.dev/rpm/mise.repo -O /etc/zypp/repos.d/mise.repo
sudo zypper refresh
sudo zypper install miseScoop exposes the mise executable through its own command shim. Configure
shell activation or mise's tool shims separately;
the current Scoop manifest does not add mise's tool-shims directory to PATH.
scoop install misewinget install jdx.mise::: info Check the Chocolatey package version before choosing it; it can lag official releases. :::
choco install miseDownload the latest release from GitHub and add the binary to your PATH.
If your shell does not support mise activate, add the shims directory (by default %LOCALAPPDATA%\mise\shims) to PATH.
mise --version
mise doctorFor the default mise.run installation before activation, use
~/.local/bin/mise --version and ~/.local/bin/mise doctor. If the version is
unexpected, check which copy is running with command -v mise on Unix or
Get-Command mise in PowerShell. Having two installation methods on PATH can
leave an older binary in use.
The examples assume mise is on PATH. For a default mise.run installation,
use ~/.local/bin/mise in the activation line instead. Add one activation line
to the startup file you actually use; avoid appending duplicates.
activation='eval "$(mise activate bash)"'
grep -qxF "$activation" ~/.bashrc 2>/dev/null || printf '%s\n' "$activation" >> ~/.bashrczshrc="${ZDOTDIR:-$HOME}/.zshrc"
activation='eval "$(mise activate zsh)"'
mkdir -p "$(dirname "$zshrc")"
grep -qxF "$activation" "$zshrc" 2>/dev/null || printf '%s\n' "$activation" >> "$zshrc"mkdir -p ~/.config/fish
activation='mise activate fish | source'
grep -qxF "$activation" ~/.config/fish/config.fish 2>/dev/null || printf '%s\n' "$activation" >> ~/.config/fish/config.fish::: tip For Homebrew and possibly other installs, mise is activated automatically, so this step is not necessary.
See MISE_FISH_AUTO_ACTIVATE=1 for more information.
:::
Use PowerShell's $PROFILE variable for the current host's profile. Create it
when missing, then add the activation line once:
if (-not (Test-Path $PROFILE)) {
New-Item -ItemType Directory -Force (Split-Path -Parent $PROFILE) | Out-Null
New-Item -ItemType File -Path $PROFILE | Out-Null
}
$activation = '(&mise activate pwsh) | Out-String | Invoke-Expression'
if (-not (Select-String -Path $PROFILE -SimpleMatch $activation -Quiet)) {
Add-Content $PROFILE $activation
}See PowerShell profiles when you use different profiles for terminals, editors, or PowerShell versions.
Nushell loads activation as a generated module. Add this to env.nu (located
at $nu.env-path) so the module exists before config.nu is parsed:
let mise_path = $nu.default-config-dir | path join mise.nu
^mise activate nu | save $mise_path --forceAdd this to config.nu (located at $nu.config-path):
use ($nu.default-config-dir | path join mise.nu)Restart Nushell after saving both files. If mise is not on PATH, use its
absolute executable path in the env.nu command. The module is regenerated at
startup so it follows mise upgrades.
Add the following to ~/.xonshrc or the Xonsh config file you use:
execx($(mise activate xonsh))For a default mise.run installation before mise is on PATH, use
execx($(~/.local/bin/mise activate xonsh)) instead. Restart Xonsh after saving.
mise updates Xonsh's environment and the process environment. If your own startup code changes PATH, keep those views consistent so subprocesses resolve the same commands as the shell.
Add the following to your rc.elv:
var mise: = (ns [&])
eval (mise activate elvish | slurp) &ns=$mise: &on-end={|ns| set mise: = $ns }
mise:activateOptionally alias mise to mise:mise for seamless integration of mise {activate,deactivate,shell}:
edit:add-var mise~ {|@args| mise:mise $@args }Adding a new shell is not hard since very little shell code is in this project. See here for how the others are implemented. If your shell isn't currently supported, I'd be happy to help you get it integrated.
::: tip Some installation methods automatically install autocompletion scripts. :::
Source your shell's rc file or restart the shell before running these examples,
so the activation added above puts mise on PATH. For a default mise.run
installation before reloading the shell, invoke ~/.local/bin/mise completion
instead of mise completion.
The mise completion command can generate autocompletion scripts for your shell.
The instructions below complete mise itself. For commands installed through the
packslip backend, see tool completions and skills.
The generated scripts are self-contained and do not require the separate usage CLI.
The simplest way to install the completion script is:
mise completion bash --installReplace bash with zsh, fish, or powershell for your shell. Alternatively, choose the path yourself:
::: code-group
# This requires bash-completion to be installed
mkdir -p ~/.local/share/bash-completion/completions/
mise completion bash > ~/.local/share/bash-completion/completions/mise# Generate into a directory owned by your user:
mkdir -p ~/.zfunc
mise completion zsh > ~/.zfunc/_mise
# Then add the fpath update to ~/.zshrc, before its existing compinit call
# (including one made by a shell framework):
fpath=(~/.zfunc $fpath)
# If ~/.zshrc does not already initialize completions, also add:
autoload -Uz compinit
compinitmkdir -p ~/.config/fish/completions
mise completion fish > ~/.config/fish/completions/mise.fish:::
If you encounter issues after installation, run:
mise doctorThis diagnoses common problems with your mise setup. See mise doctor for more information.
Use the package manager that installed mise to remove a package-managed CLI. For a standalone installation, preview the removal first:
mise implode --dry-runmise implode removes the CLI, installed tools, cache, and state, including the
system data directory when present. It keeps the user configuration directory
unless --config is passed. Inspect the listed paths before running without
--dry-run; these may be customized by environment variables.
Remove activation lines from shell startup files and any completion files you
installed separately. Project mise.toml files and host packages installed by
bootstrap are separate from mise's tool data. See directories
for the configured storage paths.