mise-en-place / everything in its place
Your dev setup.
In good order.
Declare your tool versions, environment variables, and commands in mise.toml. Use them in your shell, editor, and CI. Add machine setup with mise bootstrap when you need system packages, dotfiles, or services.
curl https://mise.run | shmacOS & Linux Installing on Windows?
# The right versions, in every project.
[tools]
node = "24"
python = "3.13"
terraform = "1.13"
Illustrative output ~/my-project
$ mise install
✓ node, python, terraform installed
Tool versions ready for this project.
- Open source & MIT licensed
- macOS, Linux & Windows
- Single CLI
01 The essentials
Start with tools. Add what you need.
$ mise use node@24
Dev tools
Install hundreds of tools, select versions per project, and switch automatically as you move between directories.
Dev tools$ mise env
Environments
Per-project env vars from mise.toml, .env files, secrets, and shell commands. Set when you enter, gone when you leave.
$ mise run test
Tasks
Build, test, lint, and deploy commands defined next to the tools and env they need, with dependencies and parallel runs.
Tasks$ mise bootstrap
Bootstrap
Apply the machine setup you declare: OS packages, dotfiles, repos, services, macOS defaults, and development tools.
BootstrapComing from asdf? Your .tool-versions already works. Enable files like .nvmrc, too.
02 Day to day
Change directory. Everything follows.
Activate mise in your shell once. From then on, entering a project puts its installed tool versions on your PATH and loads its environment variables. Leave the project and mise restores the environment for your new directory.
- Shell hooks for bash, zsh, fish, nushell, PowerShell, and more
- Shims for editors and scripts that never source your shell rc
mise execandmise-actionfor Docker and CI
03 New machine
One config for the whole machine.
Declare the packages, repositories, dotfiles, and services your machine needs, then apply them with mise bootstrap. Preview declarative resource changes with mise bootstrap plan. Add shell activation and platform-specific settings to keep machine setup alongside your tools.
- Packages through brew, apt, dnf, pacman, apk, and mas
- Dotfiles as symlinks, copies, or templates, plus single-line edits
- Remote hosts over SSH with
mise bootstrap remote
mise bootstrap --from git@github.com:you/dotfiles.git— Chef's special
Mr Boxington: fix your target/.
Give every Cargo checkout one shared, self-pruning compilation cache, locally and in CI.
04 Quickstart
Run your first project task.
- Step 1
Install mise
On macOS or Linux, use the installer below. See Windows and package manager instructions for other options.
$ curl https://mise.run | sh$ ~/.local/bin/mise --version - Step 2
Activate your shell
For zsh, add this line and restart your shell. Follow the activation guide for other shells. You can also skip activation and use
~/.local/bin/mise execor~/.local/bin/mise run.$ echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc# Restart your shell before continuing. - Step 3
Add tools
From your project directory,
mise useinstalls a tool and saves its version request inmise.toml.$ mkdir mise-example$ cd mise-example$ mise use node@24 - Step 4
Add env vars and tasks
Save a task alongside its environment, then run it. Commit
mise.tomlto share the setup. See the complete example to print both the tool version and environment.$ mise set NODE_ENV=development$ mise tasks add hello -- node -p process.env.NODE_ENV$ mise run hellodevelopment
— Ready when you are
Allez. Prep your station.
curl https://mise.run | sh