Download: v2026.11.8: Bootstrap settings plugins, block edits in bootstrap files, and argv in command wrappersv2026.11.8 ↓2026.11.82026-11-13
+37
Daily
+222
Weekly
36,185
stars
1,539
forks
46
watchers
10,116
prs
1,943
issues
677
releases
README
mise-en-place
Dev tools, env vars, and tasks in one CLI
Getting started •
Docs •
Dev tools •
Environments •
Tasks •
Bootstrap
Sponsored by
View all sponsors
What is mise?
mise (pronounced "meez", short for _mise-en-place_) manages a project's dev
tools, environment variables, and tasks from one mise.toml that works across
your shell, editor, and CI:
toml
[tools]
node = "24"
python = "3.14"
rust = "stable"
"cargo:cargo-nextest" = "0.9"
"github:BurntSushi/ripgrep" = "15"
"npm:prettier" = "3"
[env]
NODE_ENV = "development"
_.file = ".env"
_.path = "./node_modules/.bin"
[tasks.build]
description = "Build the application"
run = "npm run build"
[tasks.test]
description = "Run the test suite"
depends = ["build"]
run = "pytest && npm test"
- Install dev tools such as Node.js, Python,
Go, Rust, and Terraform from a
registry of 1,000+ tools or directly
from backends like GitHub
releases, Aqua, Cargo, npm, and PyPI, with separate versions per project.
- Load environment variables, .env
files, PATH entries, virtualenvs, and
secrets automatically as you
enter a directory.
- Run tasks defined in mise.toml or as scripts
in mise-tasks/, with dependencies, parallel execution, file watching, and
the project's tools and environment already configured.
- Set up a machine with mise bootstrap
and mise dot apply to apply system
packages, dotfiles, Git repositories, macOS defaults, and background services.
Adopt only the parts you need. Start with a single tool or task, and keep any
existing .tool-versions files as they are; mise also reads .nvmrc,
.python-version, and other
idiomatic version files
once enabled.
See the demo transcript for the
commands shown above.
Quickstart
1. Install mise
On macOS or Linux:
sh
curl -fsSL https://mise.run | sh
~/.local/bin/mise --version
On Windows, run winget install jdx.mise. For Homebrew, apt, dnf, Scoop, and
other package managers, see
Installing mise.
The installer places the binary at ~/.local/bin/mise. If ~/.local/bin is not
on your PATH yet, run ~/.local/bin/mise in place of mise until you
activate mise in step 4.
2. Run a tool without changing your shell
sh
mise exec node@24 -- node --version
v24.x.x
mise exec downloads Node.js 24 if
needed and runs the command after -- with that version on PATH. Your shell
and config files stay untouched.
3. Configure a project
Create a project directory, select Node.js 24, set an environment variable, and
add a task:
sh
mkdir my-project && cd my-project
mise use node@24
mise set NODE_ENV=development
mise tasks add hello -- node -e "console.log(process.version, process.env.NODE_ENV)"
These commands install Node.js 24 and write mise.toml:
toml
[tools]
node = "24"
[env]
NODE_ENV = "development"
[tasks.hello]
run = 'node -e "console.log(process.version, process.env.NODE_ENV)"'
Run the task wiTop issues
#15754prune treats every installed revision of an unpinned git/npm source as unused0 comments · 2026-11-15#15752npm tools fail with "requires configured install dependency 'node@lts'" under concurrent installs0 comments · 2026-11-15#15751env_cache replays the first resolution of `default` directives and `get_env` templates, ignoring the caller value0 comments · 2026-11-15#15744mise lock rejects Flux 2.9.5 → 2.10.0 when an existing aqua lock entry records SLSA provenance0 comments · 2026-11-15#15742Shim-triggered auto-install rebuilds every shim as a symlink to the invoking shim when mise isn't on PATH (macOS)0 comments · 2026-11-15
Discussions
#15750A per-tool `libc` option, as aqua has0 comments · 2026-11-15#15749`[tool_config] locked`: skip the lock pass after an install, as `MISE_LOCKED=1` does0 comments · 2026-11-15#15748Show, and optionally require, how each locked tool is verified0 comments · 2026-11-15#15747`allow_backends`: the backends a project may use, failing closed0 comments · 2026-11-15#15746`mise lock --check`: fail when a locked install would reject an entry0 comments · 2026-11-15#15745Support enabling services without changing their runtime state1 comments · 2026-11-15#15736Capacity check: 5 more verified brew issues after #15705 — how should I send them?0 comments · 2026-11-14#15729Only run depends_post when task is successful1 comments · 2026-11-14
Latest release
v2026.11.8: Bootstrap settings plugins, block edits in bootstrap files, and argv in command wrappers v2026.11.8 2026-11-13This release extends mise bootstrap with experimental settings plugins, system-wide plugin directories, block edits for system files, and repositories and hooks in mise bootstrap plan. macOS preferences move to [bootstrap.settings.macos]. Command wrappers can now read the user's arguments, and a new setting keeps private GitHub repos off mise-versions. It also fixes problems in lockfiles, hook-env performance, tasks and backends. Added Bootstrap - Bootstrap settings plugins (experimental). A plugin can now apply one program's or desktop's settings from a [bootstrap.settings.] section. The