Dev tools, env vars, and tasks in one CLI
Getting Started • Documentation • Dev Tools • Environments • Tasks
Tip
My latest project, aube just hit stable! It's the fastest Node.js package manager with strong security defaults and is compatible with npm/pnpm/yarn lockfiles!
mise prepares your development environment before each command runs. It keeps
project tools, environment variables, and tasks in one mise.toml file so new
shells, checkouts, and CI jobs all start from the same setup.
- Install and switch between dev tools like node, python, cmake, terraform, and hundreds more.
- Load environment variables per project directory, including values from
.envfiles and other sources. - Define and run tasks for building, testing, linting, and deploying projects.
The following demo shows how to install and use mise to manage multiple versions of node on the same system.
Note that calling which node gives us a real path to node, not a shim.
It also shows that you can use mise to install and many other tools such as jq, terraform, or go.
See demo transcript.
See Getting started for more options.
$ curl https://mise.run | sh
$ ~/.local/bin/mise --version
_ __
____ ___ (_)_______ ___ ____ ____ / /___ _________
/ __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
/ / / / / / (__ ) __/_____/ __/ / / /_____/ /_/ / / /_/ / /__/ __/
/_/ /_/ /_/_/____/\___/ \___/_/ /_/ / .___/_/\__,_/\___/\___/
/_/ by @jdx
2026.5.9 macos-arm64 (2026-05-15)Hook mise into your shell (pick the right one for your shell):
# note this assumes mise is located at ~/.local/bin/mise
# which is what https://mise.run does by default
echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
echo '~/.local/bin/mise activate fish | source' >> ~/.config/fish/config.fish
echo '~/.local/bin/mise activate pwsh | Out-String | Invoke-Expression' >> ~/.config/powershell/Microsoft.PowerShell_profile.ps1$ mise exec node@26 -- node -v
mise node@26.x.x ✓ installed
v26.x.x$ mise use --global node@26 go@1
$ node -v
v26.x.x
$ go version
go version go1.x.x macos/arm64See dev tools for more examples.
# mise.toml
[env]
SOME_VAR = "foo"$ mise set SOME_VAR=bar
$ echo $SOME_VAR
barNote that mise can also load .env files.
# mise.toml
[tasks.build]
description = "build the project"
run = "echo building..."$ mise run build
building...See tasks for more information.
Here is a combined example to give you an idea of how you can use mise to manage your a project's tools, environment, and tasks.
# mise.toml
[tools]
terraform = "1"
aws-cli = "2"
[env]
TF_WORKSPACE = "development"
AWS_REGION = "us-west-2"
AWS_PROFILE = "dev"
[tasks.plan]
description = "Run terraform plan with configured workspace"
run = """
terraform init
terraform workspace select $TF_WORKSPACE
terraform plan
"""
[tasks.validate]
description = "Validate AWS credentials and terraform config"
run = """
aws sts get-caller-identity
terraform validate
"""
[tasks.deploy]
description = "Deploy infrastructure after validation"
depends = ["validate", "plan"]
run = "terraform apply -auto-approve"Run it with:
mise install # install tools specified in mise.toml
mise run deployFind more examples in the mise cookbook.
See mise.en.dev
Due to the volume of issue submissions mise received, using GitHub Issues became unsustainable for the project. Instead, mise uses GitHub Discussions which provide a more community-centric platform for communication and require less management on the part of the maintainers.
Please note the following discussion categories, which match how issues are often used:
- Announcements
- Ideas: for feature requests, etc.
- Troubleshooting & Bug Reports
Thanks to Namespace for providing CI services for mise.