MISE(1) General Commands Manual MISE(1)

mise - Dev tools, env vars, and tasks in one CLI

mise [OPTIONS] [<TASK>] [<TASK_ARGS>] ... [<TASK_ARGS_LAST>] ... [COMMAND]

mise prepares your development environment before each command runs. https://github.com/jdx/mise

Continue running tasks even if one fails
Change directory before running command
Set the environment for loading `mise.<ENV>.toml`
Force the operation
How many jobs to run in parallel; values below 1 are treated as 1 [default: 8]
Environment: MISE_JOBS
Dry run, don't actually do anything
Set the profile (environment)
Suppress non-error messages
Environment: MISE_QUIET
Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
Show extra output (use -vv for even more)
Answer yes to all confirmation prompts
Sets log level to debug
Do not load any config files

Can also use `MISE_NO_CONFIG=1`

Do not load environment variables from config files

Can also use `MISE_NO_ENV=1`

Do not execute hooks from config files

Can also use `MISE_NO_HOOKS=1`

Hides elapsed time after each task completes

Default to always hide with `MISE_TASK_TIMINGS=0`

Read/write directly to stdin/stdout/stderr instead of by line
Require lockfile URLs to be present during installation

Fails if tools don't have pre-resolved URLs in the lockfile for the current platform. This prevents API calls to GitHub, aqua registry, etc. Can also be enabled via MISE_LOCKED=1 or settings.locked=true

Suppress all task output and mise non-error messages
Shows elapsed time after each task completes

Default to always show with `MISE_TASK_TIMINGS=1`

Sets log level to trace
Print help

<TASK>
Task to run.

Shorthand for `mise tasks run <TASK>`.

<TASK_ARGS>
Task arguments

Initializes mise in the current shell session
Manage tool version aliases.
Aliases: alias, aliases
Show an alias for a tool
List tool version aliases
Aliases: list
Add/update an alias for a tool/backend
Aliases: add, create
Clears an alias for a tool/backend
Aliases: rm, remove, delete, del
Manage backends
Aliases: b, backend, backend-list
List built-in backends
Aliases: list
List all the active runtime bin paths
Set up a machine for the current config in one command
Aliases: bs
Manage Linux users and groups from `[bootstrap.users]` and `[bootstrap.groups]`
Apply configured Linux users and groups
Show configured Linux user and group state
Manage Docker Compose projects from `[bootstrap.compose]`
Apply configured Docker Compose project state
Show configured Docker Compose project state
Manage dotfiles from `[dotfiles]`
Add or update dotfiles in `[dotfiles]`
Apply dotfiles from `[dotfiles]`
Show the changes needed to apply dotfiles from `[dotfiles]`
Edit a managed dotfile source
Show the status of dotfiles from `[dotfiles]`
Aliases: ls
Remove dotfiles applied from `[dotfiles]`
Manage privileged files and directories from `[bootstrap.files]` and `[bootstrap.directories]`
Apply configured privileged files and directories
Show configured privileged file and directory state
Manage the Linux host firewall from `[bootstrap.linux.firewall]`
Apply the configured Linux host firewall
Show configured Linux host firewall state
Manage Linux bootstrap config from `[bootstrap.linux]`
Manage systemd user services from `[bootstrap.linux.systemd.units]`
Aliases: systemd
Manage macOS bootstrap config from `[bootstrap.macos]`
Manage macOS defaults from `[bootstrap.macos.defaults]`
Manage macOS LaunchAgents from `[bootstrap.macos.launchd.agents]`
Aliases: launchd
Manage mise shell activation from `[bootstrap.mise_shell_activate]`
Aliases: shell
Manage bootstrap system packages from `[bootstrap.packages]`
Apply system packages from `[bootstrap.packages]`
Aliases: i, install
Manage Homebrew taps used by bootstrap packages
Add a Homebrew tap URL to [bootstrap.brew.taps]
Remove Homebrew tap URLs from [bootstrap.brew.taps]
Aliases: remove, rm
Import installed system packages into `[bootstrap.packages]`
Prune installed system packages no longer declared in `[bootstrap.packages]`
Show the status of system packages from `[bootstrap.packages]`
Aliases: ls
Upgrade installed bootstrap packages from `[bootstrap.packages]`
Aliases: up
Add bootstrap packages to [bootstrap.packages] and install them
Aliases: u
Show the changes declarative bootstrap resources would make
Manage package manager plugins declared in `[bootstrap.plugins]`
Bootstrap one or more machines over OpenSSH
Manage git repo checkouts from `[bootstrap.repos]`
Inspect bootstrap secret inputs without revealing their values
Show whether declared bootstrap secret inputs are available
Manage Linux system services from `[bootstrap.services]`
Apply configured Linux system service state
Show configured Linux system service state
Show the aggregate bootstrap status
Aliases: ls
Manage current-user bootstrap settings from `[bootstrap.user]`
Manage the mise cache
Deletes all cache files in mise
Aliases: c, clean
Show the cache directory path
Aliases: dir
Removes stale mise cache files
Aliases: p
Inspect output cache entries for a task
Generate shell completions
Aliases: complete, completions
Manage config files
Aliases: cfg, toml
Display the value of a setting in a mise.toml file
List config files currently in use
Aliases: list
Set the value of a setting in a mise.toml file
Disable mise for current shell session
Check mise installation for possible problems
Aliases: dr
Print the current PATH entries mise is providing
Aliases: paths
Starts a new shell with the mise environment built from the current configuration
Exports env vars to activate mise a single time
Aliases: e
Execute a command with tool(s) set
Aliases: x
Formats mise.toml
Generate files for various tools/services
Aliases: gen, g
Generate a mise.toml file
Generate a devcontainer to execute mise
Generate a git pre-commit hook
Aliases: pre-commit
Generate a GitHub Action workflow file
Generate a script to download+execute mise
Generate documentation for tasks in a project
Generates shims to run mise tasks
Generate a tool stub for HTTP-based tools
Removes mise CLI and all related data
Edit mise.toml interactively
Install a tool version
Aliases: i
Install a tool version to a specific path
Gets the latest available version for a plugin
Symlinks a tool version into mise
Aliases: ln
Update lockfile checksums and URLs for all specified platforms
List installed and active tool versions
Aliases: list
List runtime versions available for install.
Aliases: list-all, list-remote
Run Model Context Protocol (MCP) server
[experimental] Build OCI container images from a mise.toml
[experimental] Build an OCI image from the current mise.toml
[experimental] Build an OCI image and push it to a registry
[experimental] Build an OCI image from the current mise.toml and run a command in it
Shows outdated tool versions
Show the individuals supporting mise as Patron-tier members
Manage plugins
Aliases: p, plugin, plugin-list
Install a plugin
Aliases: i, a, add
Symlinks a plugin into mise
Aliases: ln
List installed plugins
Aliases: list
Aliases: list-remote, list-all
Removes a plugin
Aliases: remove, rm
Updates a plugin to the latest version
Aliases: up, upgrade
[experimental] Manage project dependencies
Aliases: dep, prepare
Add a dependency
Install all project dependencies
Remove a dependency
Delete unused versions of tools
List available tools to install
Creates new shims based on bin paths from currently installed tools.
Run task(s)
Aliases: r
Search for tools in the registry
Updates mise itself.
Set environment variables in mise.toml
Aliases: ev, env-vars
Manage settings
Adds a setting to the configuration file
Show a current setting
Show current settings
Aliases: list
Add/update a setting
Aliases: create
Clears a setting
Aliases: rm, remove, delete, del
Sets a tool version for the current session.
Aliases: sh
Manage shell aliases.
Show the command for a shell alias
List shell aliases
Aliases: list
Add/update a shell alias
Aliases: add, create
Removes a shell alias
Aliases: rm, remove, delete, del
Show the companies sponsoring mise and the jdx.dev open source tools
Synchronize tools from other version managers with mise
Symlinks all tool versions from an external tool into mise
Symlinks all tool versions from an external tool into mise
Symlinks all ruby tool versions from an external tool into mise
Manage tasks
Aliases: t, task
Create a new task
Display a tree visualization of a dependency graph
Edit a task with $EDITOR
[experimental] Inspect the workspace project graph
Get information about a task
List available tasks to execute
Run task(s)
Aliases: r
Validate tasks for common errors and issues
Test a tool installs and executes
Display git provider tokens mise will use
Display the Forgejo token mise will use for a given host
Display the GitHub token mise will use for a given host
Display the GitLab token mise will use for a given host
Gets information about a tool
Execute a tool stub
Marks a config file as trusted
Removes installed tool versions
Remove environment variable(s) from the config file.
Remove explicit trust for a config
Removes installed tool versions from mise.toml
Aliases: rm, remove
Upgrades outdated tools
Aliases: up
Installs a tool and adds the version to mise.toml.
Aliases: u
Display the version of mise
Aliases: v
Run task(s) and watch for changes to rerun it
Aliases: w
Display the installation path for a tool
Shows the path that a tool's bin points to.

Initializes mise in the current shell session

This should go into your shell's rc file or login shell. Otherwise, it will only take effect in the current session. (e.g. ~/.zshrc, ~/.zprofile, ~/.zshenv, ~/.bashrc, ~/.bash_profile, ~/.profile, ~/.config/fish/config.fish, or $PROFILE for powershell)

Typically, this can be added with something like the following:


echo 'eval "$(mise activate zsh)"' >> ~/.zshrc

However, this requires that "mise" is in your PATH. If it is not, you need to specify the full path like this:


echo 'eval "$(/path/to/mise activate zsh)"' >> ~/.zshrc

Customize status output with `status` settings.

Usage: mise activate [OPTIONS] [<SHELL_TYPE>]

Options:

Suppress non-error messages
Shell type to generate the script for
Do not automatically call hook-env

This can be helpful for debugging mise. If you run `eval "$(mise activate --no-hook-env)"`, then you can call `mise hook-env` manually which will output the env vars to stdout without actually modifying the environment. That way you can do things like `mise hook-env --trace` to get more information or just see the values that hook-env is outputting.

Use shims instead of modifying PATH Effectively the same as:


PATH="$HOME/.local/share/mise/shims:$PATH"

`mise activate --shims` does not support all the features of `mise activate`. See https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path for more information

Show "mise: <TOOL>@<VERSION>" message when changing directories
Print help Arguments:
<SHELL_TYPE>
Shell type to generate the script for

Manage tool version aliases.

Usage: mise tool-alias [OPTIONS] [COMMAND]

Options:

Filter aliases by tool
Don't show table header
Print help

Show an alias for a tool

This is the contents of a tool_alias.<TOOL> entry in ~/.config/mise/config.toml

Usage: mise tool-alias get [OPTIONS] <TOOL> <ALIAS>

Options:

Print help Arguments:
<TOOL>
The tool to show the alias for
<ALIAS>
The alias to show

List tool version aliases Shows the aliases that can be specified. These can come from user config or from plugins in `bin/list-aliases`.

For user config, aliases are defined like the following in `~/.config/mise/config.toml`:


[tool_alias.node.versions]
lts = "22.0.0"

Usage: mise tool-alias ls [OPTIONS] [<TOOL>]

Options:

Don't show table header
Print help Arguments:
<TOOL>
Show aliases for <TOOL>

Add/update an alias for a tool/backend

This modifies the contents of ~/.config/mise/config.toml

Usage: mise tool-alias set [OPTIONS] <TOOL> <ALIAS> [<VALUE>]

Options:

Print help Arguments:
<TOOL>
The tool/backend to set the alias for
<ALIAS>
The alias to set
<VALUE>
The value to set the alias to

Clears an alias for a tool/backend

This modifies the contents of ~/.config/mise/config.toml

Usage: mise tool-alias unset [OPTIONS] <TOOL> [<ALIAS>]

Options:

Print help Arguments:
<TOOL>
The tool/backend to remove the alias from
<ALIAS>
The alias to remove

Manage backends

Usage: mise backends [OPTIONS] [COMMAND]

Options:

Print help

List built-in backends

Usage: mise backends ls [OPTIONS]

Options:

Print help

List all the active runtime bin paths

Usage: mise bin-paths [OPTIONS] [<TOOL@VERSION>] ...

Options:

Output executable names instead of bin directories
Output executable entries in JSON format (implies --bin-names)
Print help Arguments:
<TOOL@VERSION>
Tool(s) to look up e.g.: ruby@3

Set up a machine for the current config in one command

Runs the bootstrap steps for the current config in order:

0. `mise bootstrap accounts apply` — converge `[bootstrap.users]` and
`[bootstrap.groups]` (Linux) 1. `mise bootstrap plugins apply` — install `[bootstrap.plugins]`
1.7. `[bootstrap.hooks.pre-packages]` — optional setup hook 2. Install built-in-manager entries from `[bootstrap.packages]` 3. `mise bootstrap files apply` — converge `[bootstrap.files]` and
`[bootstrap.directories]` 4. `mise bootstrap services apply` — converge `[bootstrap.services]`
systemd system services (Linux) 5. `mise bootstrap firewall apply` — converge `[bootstrap.linux.firewall]`
host firewall policy and rules (Linux) 6. `mise bootstrap compose apply` — converge `[bootstrap.compose]`
Docker Compose projects 7. `mise bootstrap repos apply` — clone/converge `[bootstrap.repos]`
surrounded by `pre-repos`/`post-repos` hooks 8. `mise bootstrap dotfiles apply` — apply dotfiles from `[dotfiles]`
surrounded by `pre-dotfiles`/`post-dotfiles` hooks 9. `mise bootstrap mise-shell-activate apply` — configure shell activation
from `[bootstrap.mise_shell_activate]` 10. `mise bootstrap macos defaults apply` — write
`[bootstrap.macos.defaults]` entries (macOS)
surrounded by `pre-defaults`/`post-defaults` hooks 11. `mise bootstrap macos launchd-agents apply` — install/load
`[bootstrap.macos.launchd.agents]` 12. `mise bootstrap linux systemd-units apply` — install/start
`[bootstrap.linux.systemd.units]` 13. `mise bootstrap user apply` — set `[bootstrap.user].login_shell`
(Unix)
surrounded by `pre-user`/`post-user` hooks 14. `mise install` — install missing tools from `[tools]`
surrounded by `pre-tools`/`post-tools` hooks; package-plugin entries
from `[bootstrap.packages]` install afterward, followed by
`[bootstrap.hooks.post-packages]` 15. `mise run bootstrap` — if a task named `bootstrap` is defined 16. `[bootstrap.hooks.final]` — optional final hook

The declarative steps converge — anything already in its desired state is skipped, so re-running is safe. The `bootstrap` task runs on every invocation; keep it idempotent. Use it for any project-specific setup that doesn't fit the declarative sections (seeding databases, auth flows, etc.) — it runs with the installed tools on PATH.

Use `--skip <part>` to skip named parts, or `--only <part>` to run just named parts. Both flags can be repeated or comma-separated, but they cannot be used together.

Usage: mise bootstrap [OPTIONS] [COMMAND]

Options:

Clone a git repository and bootstrap from its configuration
Directory used for the repository cloned by --from
Print what would happen without installing anything
Skip confirmation prompts
Skip configured repos with local changes instead of failing
Overwrite existing files that conflict with whole-file dotfile entries
Run only one or more bootstrap parts

Can be passed multiple times or as a comma-separated list. Cannot be used with `--skip`.

Prompt securely for missing bootstrap secret inputs
Skip one or more bootstrap parts

Can be passed multiple times or as a comma-separated list.

Refresh package manager metadata and update configured repos
Print help

Manage Linux users and groups from `[bootstrap.users]` and `[bootstrap.groups]`

Usage: mise bootstrap accounts [OPTIONS] <COMMAND>

Options:

Print help

Apply configured Linux users and groups

Usage: mise bootstrap accounts apply [OPTIONS]

Options:

Print what would change without changing anything
Skip the confirmation prompt
Print help

Show configured Linux user and group state

Usage: mise bootstrap accounts status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 when any account is not converged
Print help

Manage Docker Compose projects from `[bootstrap.compose]`

Usage: mise bootstrap compose [OPTIONS] <COMMAND>

Options:

Print help

Apply configured Docker Compose project state

Usage: mise bootstrap compose apply [OPTIONS]

Options:

Print what would change without changing anything
Skip the confirmation prompt
Print help

Show configured Docker Compose project state

Usage: mise bootstrap compose status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 when any Compose project is not converged
Print help

Manage dotfiles from `[dotfiles]`

Usage: mise bootstrap dotfiles [OPTIONS] <COMMAND>

Options:

Print help

Add or update dotfiles in `[dotfiles]`

If the target is already managed, this updates its source from the live target. Otherwise it creates a `[dotfiles]` entry and seeds the source under `dotfiles.root` unless `--source` is provided.

Usage: mise bootstrap dotfiles add [OPTIONS] [<TARGET>] ...

Options:

Update the sources of every changed file managed in copy mode
Overwrite existing sources without prompting
Write to the global config
Write to the local config instead of the global config
Dotfile mode to write
Print the config/source updates without writing anything
Add the entry without applying it
Write to this config file or directory
Source path to use for a single target
Skip the confirmation prompt
Print help Arguments:
<TARGET>
Targets to add or update

Apply dotfiles from `[dotfiles]`

Applies configured whole-file entries and edits that aren't in their desired state. Whole-file entries may symlink, copy, or render templates. Edit entries manage a marker-delimited block or a single line in a file mise doesn't otherwise own.

Usage: mise bootstrap dotfiles apply [OPTIONS] [<TARGET>] ...

Options:

Overwrite existing files that conflict with whole-file dotfile entries
Print the actions that would run without writing anything
Skip the confirmation prompt
Print help Arguments:
<TARGET>
Only apply these targets

Show the changes needed to apply dotfiles from `[dotfiles]`

Usage: mise bootstrap dotfiles diff [OPTIONS] [<TARGET>] ...

Options:

Print help Arguments:
<TARGET>
Only show these targets

Edit a managed dotfile source

Usage: mise bootstrap dotfiles edit [OPTIONS] <TARGET>

Options:

Apply this target after the editor exits
Dotfile mode to use if the target is not yet managed
Source path to use if the target is not yet managed
Skip the confirmation prompt when adding an unmanaged target
Print help Arguments:
<TARGET>
Target to edit

Show the status of dotfiles from `[dotfiles]`

Usage: mise bootstrap dotfiles status [OPTIONS] [<TARGET>] ...

Options:

Output in JSON format
Exit with code 1 if any configured dotfiles are not in their desired state (missing, source missing, differs)
Print help Arguments:
<TARGET>
Only show these targets

Remove dotfiles applied from `[dotfiles]`

Removes configured whole-file entries and edits while preserving files mise cannot identify as managed. Modified copies, templates, and plain-line edits require `--force`.

Usage: mise bootstrap dotfiles unapply [OPTIONS] [<TARGET>] ...

Options:

Remove modified or otherwise ambiguous managed files and lines
Print the actions that would run without writing anything
Skip the confirmation prompt
Print help Arguments:
<TARGET>
Only unapply these targets

Manage privileged files and directories from `[bootstrap.files]` and `[bootstrap.directories]`

Usage: mise bootstrap files [OPTIONS] <COMMAND>

Options:

Print help

Apply configured privileged files and directories

Usage: mise bootstrap files apply [OPTIONS]

Options:

Print what would change without changing anything
Skip the confirmation prompt
Prompt securely for missing bootstrap secret inputs
Print help

Show configured privileged file and directory state

Usage: mise bootstrap files status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 when any resource is not converged
Prompt securely for missing bootstrap secret inputs
Print help

Manage the Linux host firewall from `[bootstrap.linux.firewall]`

Usage: mise bootstrap firewall [OPTIONS] <COMMAND>

Options:

Print help

Apply the configured Linux host firewall

Usage: mise bootstrap firewall apply [OPTIONS]

Options:

Print what would change without changing anything
Skip the confirmation prompt
Print help

Show configured Linux host firewall state

Usage: mise bootstrap firewall status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 when the firewall is not converged
Print help

Manage Linux bootstrap config from `[bootstrap.linux]`

Usage: mise bootstrap linux [OPTIONS] <COMMAND>

Options:

Print help

Manage systemd user services from `[bootstrap.linux.systemd.units]`

Usage: mise bootstrap linux systemd-units [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap linux systemd-units apply [OPTIONS]

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Print help

Usage: mise bootstrap linux systemd-units status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured systemd user service is not in its desired state
Print help

Manage macOS bootstrap config from `[bootstrap.macos]`

Usage: mise bootstrap macos [OPTIONS] <COMMAND>

Options:

Print help

Manage macOS defaults from `[bootstrap.macos.defaults]`

Usage: mise bootstrap macos defaults [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap macos defaults apply [OPTIONS]

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Print help

Usage: mise bootstrap macos defaults status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured defaults are not in their desired state
Print help

Manage macOS LaunchAgents from `[bootstrap.macos.launchd.agents]`

Usage: mise bootstrap macos launchd-agents [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap macos launchd-agents apply [OPTIONS]

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Print help

Usage: mise bootstrap macos launchd-agents status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured LaunchAgent is not in its desired state
Print help

Manage mise shell activation from `[bootstrap.mise_shell_activate]`

Usage: mise bootstrap mise-shell-activate [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap mise-shell-activate apply [OPTIONS]

Options:

Print the actions that would run without writing anything
Skip the confirmation prompt
Print help

Usage: mise bootstrap mise-shell-activate status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured shell activation is not in its desired state
Print help

Manage bootstrap system packages from `[bootstrap.packages]`

Usage: mise bootstrap packages [OPTIONS] <COMMAND>

Options:

Print help

Apply system packages from `[bootstrap.packages]`

Checks which configured packages are missing and installs them with the system package manager. Built-in system managers may elevate with sudo when not running as root (see `system_packages.sudo`); package plugins never do.

Packages can also be given explicitly in `manager:package` form (e.g. `apk:zlib-dev`, `apt:curl`, `brew:jq`); they are installed whether or not they appear in the config. Explicit packages and `--manager` scope the run to packages only. `install` is accepted as an alias for this command.

Usage: mise bootstrap packages apply [OPTIONS] [<PACKAGE>] ...

Options:

Only install packages for this built-in or plugin manager
Print the commands that would run without running them
Skip the confirmation prompt
Refresh package manager metadata first (apk: `--update-cache`, apt: `apt-get update`)
Print help Arguments:
<PACKAGE>
Packages in `manager:package` form; defaults to everything configured in [bootstrap.packages]

Manage Homebrew taps used by bootstrap packages

These commands edit `[bootstrap.brew.taps]` so tapped formulae and casks can be fetched directly by mise without a Homebrew installation.

Usage: mise bootstrap packages brew [OPTIONS] <COMMAND>

Options:

Print help

Add a Homebrew tap URL to [bootstrap.brew.taps]

Usage: mise bootstrap packages brew tap [OPTIONS] <TAP> [<URL>]

Options:

Write to the local config instead of the global config
Print the config change without writing it
Write to this config file or directory
Print help Arguments:
<TAP>
Tap name, e.g. `owner/repo`
<URL>
GitHub URL for the tap. Defaults to https://github.com/<owner>/homebrew-<repo>.git

Remove Homebrew tap URLs from [bootstrap.brew.taps]

Usage: mise bootstrap packages brew untap [OPTIONS] <TAPS> ...

Options:

Write to the local config instead of the global config
Print the config change without writing it
Write to this config file or directory
Print help Arguments:
<TAPS>
Tap name(s), e.g. `owner/repo`

Import installed system packages into `[bootstrap.packages]`

Currently supports Homebrew formulae only. By default, imports linked formulae whose active keg receipt says they were installed on request. Pass `--all` to import every linked formula, including dependencies.

Usage: mise bootstrap packages import [OPTIONS]

Options:

Write to the config file for this environment (mise.<ENV>.toml)
Write to the global config (~/.config/mise/config.toml)
Only import packages for this manager. Currently only `brew` is supported.
Default: brew
Import every linked formula, including dependencies
Print the config change without writing config
Write to this config file or directory
Print help

Prune installed system packages no longer declared in `[bootstrap.packages]`

Supports Homebrew formulae, conservatively removable mise-owned casks, and packages installed by package plugins that implement `PackageUninstall`. Pruning keeps packages needed by the current config or by trusted, loadable tracked configs. Plugin packages that were already installed before mise first applied them are never claimed or removed.

Usage: mise bootstrap packages prune [OPTIONS]

Options:

Only prune packages for this manager
Default: brew
Print what would be removed without deleting anything
Skip the confirmation prompt
Print help

Show the status of system packages from `[bootstrap.packages]`

Usage: mise bootstrap packages status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured packages are not in their desired state
Print help

Upgrade installed bootstrap packages from `[bootstrap.packages]`

Refreshes package manager metadata and upgrades the configured packages that are already installed: apk/apt/dnf/pacman upgrade to the newest available version (apk, apt, and dnf honor a version pinned in config), brew pours the formula's current bottle and replaces the old keg, brew-cask installs the current cask artifact, flatpak and flatpak-user update applications and runtimes, and mas upgrades App Store apps. Packages that are not installed yet are skipped — use `mise bootstrap packages apply` for those.

Packages can also be given explicitly in `manager:package` form.

Usage: mise bootstrap packages upgrade [OPTIONS] [<PACKAGE>] ...

Options:

Only upgrade packages for this built-in or plugin manager
Print the commands that would run without running them
Skip the confirmation prompt
Print help Arguments:
<PACKAGE>
Packages in `manager:package` form; defaults to everything configured in [bootstrap.packages]

Add bootstrap packages to [bootstrap.packages] and install them

Like `mise use` for tools: writes `"manager:package" = "version"` entries to mise.toml (the local config by default, the global one with `-g`) and then installs whatever is missing.

Versions are pinned with `@`: `mise bootstrap packages use apt:curl@8.5.0-2`. Without `@` (or with `@latest`) no pin is written. brew formulae and casks version through their names instead (for example `brew:postgresql@17`, `brew-cask:temurin@17`), where `@` is part of the Homebrew name rather than a mise version selector. mas uses numeric ADAM IDs and does not support pins.

Usage: mise bootstrap packages use [OPTIONS] <PACKAGE> ...

Options:

Write to the config file for this environment (mise.<ENV>.toml)
Write to the global config (~/.config/mise/config.toml) instead of the local one
Print the commands that would run without writing config or installing
Write to this config file or directory
Skip the confirmation prompt
Print help Arguments:
<PACKAGE>
Packages in `manager:package[@version]` form

Show the changes declarative bootstrap resources would make

Usage: mise bootstrap plan [OPTIONS]

Options:

Output a stable machine-readable plan in JSON format
Exit 2 when the plan contains changes, 0 when unchanged, and 1 on errors
Prompt securely for missing bootstrap secret inputs
Print help

Manage package manager plugins declared in `[bootstrap.plugins]`

Usage: mise bootstrap plugins [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap plugins apply [OPTIONS]

Options:

Print what would happen without installing plugins
Print help

Usage: mise bootstrap plugins status [OPTIONS]

Options:

Exit with code 1 if a declared plugin is missing
Print help

Bootstrap one or more machines over OpenSSH

Usage: mise bootstrap remote [OPTIONS] [<TARGET>] ...

Options:

Select every configured inventory host
Explicit remote shell command that installs mise and places it on PATH
SSH connection timeout in seconds
Default: 10
Dereference one source-relative symbolic link; repeat for multiple links
Dereference every symbolic link in the source archive
Additional archive pattern to exclude; repeat for multiple patterns
Stop after the first failed target
Allow remote dotfile conflicts to be replaced
Ad-hoc SSH destination (`[user@]host`); repeat for multiple hosts
SSH identity file override
Print the remote bootstrap changes without applying them
Install the provisioned mise on each host instead of only staging it

Defaults to `~/.local/bin/mise`; pass `--install-mise=<PATH>` for another path.

Keep the remote staging directory for debugging
Local mise binary to upload (escape hatch for custom architectures)
Do not install mise on the host, even when the selected hosts configure it
Run only one or more remote bootstrap parts
SSH port override
Prompt securely for missing secret inputs on the remote host
Config environments to load on the remote host; repeat or delimit with commas (for example, ci,dotfiles)
Existing mise executable name or path; relative paths use the staged project
Skip one or more remote bootstrap parts
Local directory archived and sent to each target
OpenSSH `-o` option; repeat for multiple options
Select configured hosts with this tag; repeat to match any tag
Refresh package manager metadata and update configured repos remotely
Skip remote confirmation prompts
Print help Arguments:
<TARGET>
Inventory host names from `[bootstrap.remote.hosts]`

Manage git repo checkouts from `[bootstrap.repos]`

Usage: mise bootstrap repos [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap repos apply [OPTIONS]

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Skip repos with local changes instead of failing
Print help

Usage: mise bootstrap repos exec [OPTIONS] [<PATH>] ... <COMMAND> ...

Options:

Continue running in other repos after a command fails
Print the commands that would run without running them
Print help Arguments:
<PATH>
Run only in matching configured or expanded paths
<COMMAND>
Command and arguments to run in each repo

Usage: mise bootstrap repos status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured repo is not in its desired state
Print help

Usage: mise bootstrap repos update [OPTIONS] [<PATH>] ...

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Skip repos with local changes instead of failing
Print help Arguments:
<PATH>
Update only matching configured or expanded paths

Inspect bootstrap secret inputs without revealing their values

Usage: mise bootstrap secrets [OPTIONS] <COMMAND>

Options:

Print help

Show whether declared bootstrap secret inputs are available

Usage: mise bootstrap secrets status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if a declared secret input is unavailable
Print help

Manage Linux system services from `[bootstrap.services]`

Usage: mise bootstrap services [OPTIONS] <COMMAND>

Options:

Print help

Apply configured Linux system service state

Usage: mise bootstrap services apply [OPTIONS]

Options:

Print what would change without changing anything
Skip the confirmation prompt
Print help

Show configured Linux system service state

Usage: mise bootstrap services status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 when any service is not converged
Print help

Show the aggregate bootstrap status

Usage: mise bootstrap status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured bootstrap state is not in its desired state
Prompt securely for missing bootstrap secret inputs
Print help

Manage current-user bootstrap settings from `[bootstrap.user]`

Usage: mise bootstrap user [OPTIONS] <COMMAND>

Options:

Print help

Usage: mise bootstrap user apply [OPTIONS]

Options:

Print the commands that would run without running them
Skip the confirmation prompt
Print help

Usage: mise bootstrap user status [OPTIONS]

Options:

Output in JSON format
Exit with code 1 if any configured user setting is not in its desired state
Print help

Manage the mise cache

Run `mise cache` with no args to view the current cache directory.

Usage: mise cache [OPTIONS] [COMMAND]

Options:

Print help

Deletes all cache files in mise

Usage: mise cache clear [OPTIONS] [<TOOL>] ...

Options:

Mark all cache files as old
Clear output cache entries for a task name or pattern
Print help Arguments:
<TOOL>
Tool(s) to clear cache for e.g.: node, python

Show the cache directory path

Usage: mise cache path [OPTIONS]

Options:

Print help

Removes stale mise cache files

By default, this command will remove files that have not been accessed in 30 days. Change this with the MISE_CACHE_PRUNE_AGE environment variable.

Usage: mise cache prune [OPTIONS] [<TOOL>] ...

Options:

Show pruned files
Just show what would be pruned
Print help Arguments:
<TOOL>
Tool(s) to prune cache for e.g.: node, python

Inspect output cache entries for a task

Usage: mise cache task [OPTIONS] <TASK>

Options:

Output in JSON format
Print help Arguments:
<TASK>
Task name or pattern to inspect

Generate shell completions

Usage: mise completion [OPTIONS] [<SHELL>]

Options:

Shell type to generate completions for
Retained for compatibility with older completion generators.

usage-rs's built-in bash script is self-contained, so this is now a no-op.

Retained for compatibility with older completion generators.

Completions now always use usage-rs's built-in protocol, so this is a no-op.

Install the script where this shell looks for it, instead of printing it

Writes the script file and nothing else: no shell rc file and no PowerShell profile is edited. Where a shell needs a one-time line of its own — zsh's `fpath+=`, PowerShell's dot-source — it is printed for you to add.

Replace a file at the target path that mise did not write
Print help Arguments:
<SHELL>
Shell type to generate completions for

Manage config files

Usage: mise config [OPTIONS] [COMMAND]

Options:

Output in JSON format
Do not print table header
List all tracked config files
Print help

Display the value of a setting in a mise.toml file

Usage: mise config get [OPTIONS] [<KEY>]

Options:

The path to the mise.toml file to read

Can be a file path or directory. If a directory is provided, the config file in that directory is used.

If not provided, the nearest mise.toml file will be used

Read the global config file.
Read the system config file.
Print help Arguments:
<KEY>
The path of the config to display

List config files currently in use

Usage: mise config ls [OPTIONS]

Options:

Output in JSON format
Do not print table header
List all tracked config files
Print help

Set the value of a setting in a mise.toml file

Usage: mise config set [OPTIONS] <KEY> [<VALUE>]

Options:

The path to the mise.toml file to edit

Can be a file path or directory. If a directory is provided, the config file in that directory is used.

If not provided, the nearest mise.toml file will be used

Edit the global config file.
Edit the system config file.
Append the value without duplicating an existing entry.
Remove the value from an existing collection.
Default: infer
Print help Arguments:
<KEY>
The path of the config to display
<VALUE>
The value to set the key to (optional if provided as KEY=VALUE)

Disable mise for current shell session

This can be used to temporarily disable mise in a shell session.

Usage: mise deactivate [OPTIONS]

Options:

Print help

Check mise installation for possible problems

Usage: mise doctor [OPTIONS] [COMMAND]

Options:

Print help

Print the current PATH entries mise is providing

Usage: mise doctor path [OPTIONS]

Options:

Print all entries including those not provided by mise
Print help

Starts a new shell with the mise environment built from the current configuration

This is an alternative to `mise activate` that allows you to explicitly start a mise session. It will have the tools and environment variables in the configs loaded. Note that changing directories will not update the mise environment.

Usage: mise en [OPTIONS] [<DIR>]

Options:

Shell to start

Defaults to $SHELL

Print help Arguments:
<DIR>
Directory to start the shell in
Default: .

Exports env vars to activate mise a single time

Use this if you don't want to permanently install mise. It's not necessary to use this if you have `mise activate` in your shell rc file.

Usage: mise env [OPTIONS] [<TOOL@VERSION>] ...

Options:

Output in dotenv format
Output in JSON format
Shell type to generate environment variables for
Output in JSON format with additional information (source, tool)
Only show redacted environment variables
Only show values of environment variables
Print help Arguments:
<TOOL@VERSION>
Tool(s) to use

Execute a command with tool(s) set

use this to avoid modifying the shell session or running ad-hoc commands with mise tools set.

Tools will be loaded from mise.toml, though they can be overridden with <RUNTIME> args Note that only the plugin specified will be overridden, so if a `mise.toml` file includes "node 20" but you run `mise exec python@3.11`; it will still load node@20.

The "--" separates runtimes from the commands to pass along to the subprocess.

Usage: mise exec [OPTIONS] [<TOOL@VERSION>] ... [<COMMAND>] ...

Options:

Command string to execute
Number of jobs to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_JOBS
Allow specific env var through (implies --deny-env for everything else) Supports wildcards, e.g. --allow-env='MYAPP_*'
Allow network to specific host (implies --deny-net for everything else) macOS only in v1; on Linux falls back to allowing all network
Allow reads from specific path (implies --deny-read for everything else)
Allow writes to specific path (implies --deny-write for everything else)
Block reads, writes, network, and env vars
Block env var inheritance (only PATH, HOME, USER, SHELL, TERM, LANG pass through)
Block all network access
Block filesystem reads (system libs and tool dirs still accessible)
Block all filesystem writes
Bypass the environment cache and recompute the environment
Skip automatic dependency preparation
Connect backend install command stdin/stdout/stderr directly to the terminal Implies --jobs=1
Print help Arguments:
<TOOL@VERSION>
Tool(s) to start e.g.: node@20 python@3.10
<COMMAND>
Command string to execute (same as --command)

Formats mise.toml

Sorts keys and cleans up whitespace in mise.toml

Usage: mise fmt [OPTIONS]

Options:

Format all files from the current directory
Check if the configs are formatted, no formatting is done
Read config from stdin and write its formatted version into stdout
Print help

Generate files for various tools/services

Usage: mise generate [OPTIONS] <COMMAND>

Options:

Print help

Generate a mise.toml file

Usage: mise generate config [OPTIONS] [<PATH>]

Options:

Generate the global config file (~/.config/mise/config.toml)
Show what would be generated without writing to file
Path to a .tool-versions file to import tools from
Print help Arguments:
<PATH>
Path to the config file to create

Generate a devcontainer to execute mise

Usage: mise generate devcontainer [OPTIONS]

Options:

The image to use for the devcontainer
Bind the mise-data-volume to the devcontainer
The name of the devcontainer
write to .devcontainer/devcontainer.json
Print help

Generate a git pre-commit hook

This command generates a git pre-commit hook that runs a mise task like `mise run pre-commit` when you commit changes to your repository.

Staged files are passed to the task as `STAGED`.

For more advanced pre-commit functionality, see mise's sister project: https://hk.jdx.dev/

Usage: mise generate git-pre-commit [OPTIONS] [<MISE_ARG>] ...

Options:

The task to run when the pre-commit hook is triggered
Default: pre-commit
write to .git/hooks/pre-commit and make it executable
Which hook to generate (saves to .git/hooks/$hook)
Default: pre-commit
Print help Arguments:
<MISE_ARG>
mise flags to embed in the generated hook, given after `--`

These are inserted between `mise` and `run`, so the hook carries the same context you would pass on the command line. Useful when the config is not at the repository root, since git runs hooks from the top level: `-- -C subdir` makes the hook find it.

Generate a GitHub Action workflow file

This command generates a GitHub Action workflow file that runs a mise task like `mise run ci` when you push changes to your repository.

Usage: mise generate github-action [OPTIONS]

Options:

The task to run when the workflow is triggered
Default: ci
write to .github/workflows/$name.yml
the name of the workflow to generate
Default: ci
Print help

Generate a script to download+execute mise

This is designed to be used in a project where contributors may not have mise installed.

Renamed from `mise generate bootstrap`, which read as a form of `mise bootstrap` (machine setup). The old name still works but is deprecated and will be removed in mise 2027.9.0.

Usage: mise generate install-script [OPTIONS]

Options:

Sandboxes mise internal directories like MISE_DATA_DIR and MISE_CACHE_DIR into a `.mise` directory in the project

This is necessary if users may use a different version of mise outside the project.

Specify mise version to fetch
instead of outputting the script to stdout, write to a file and make it executable
Directory to put localized data into
Default: .mise
Also write a Windows launcher, `<WRITE>.cmd`

Windows cannot execute the `#!/usr/bin/env bash` script, so a contributor who clones the project on Windows has nothing to run without this.

Generated on every host, not only on Windows: the file is committed, and whoever runs it on Windows is not the person who generated it. Requires `--write`, since stdout cannot carry two files.

Print help

Generate documentation for tasks in a project

Usage: mise generate task-docs [OPTIONS]

Options:

inserts the documentation into an existing file

This will look for a special comment, `<!-- mise-tasks -->`, and replace it with the generated documentation. It will replace everything between the comment and the next comment, `<!-- /mise-tasks -->` so it can be run multiple times on the same file to update the documentation. The file must already contain both comments; mise errors instead of modifying the file if they are missing.

write only an index of tasks, intended for use with `--multi`
render each task as a separate document, requires `--output` to be a directory
writes the generated docs to a file/directory
root directory to search for tasks
Default: simple
Print help

Generates shims to run mise tasks

By default, this will build shims like ./bin/<task>. These can be paired with `mise generate install-script` so contributors to a project can execute mise tasks without installing mise into their system. When a parent and nested task both exist, the parent stub is written to `<parent>/_default`.

Usage: mise generate task-stubs [OPTIONS]

Options:

Directory to create task stubs inside of
Default: bin
Path to a mise bin to use when running the task stub.

Use `--mise-bin=./bin/mise` to use a mise bin generated from `mise generate install-script`

On Windows a path is run as written, so that script needs its own launcher beside it: generate it with `mise generate install-script --write ./bin/mise --windows`. The default `mise` is a bare name and resolves off PATH, which needs nothing extra.

Default: mise
What to write beside each stub for Windows to launch

`cmd` writes `<task>.cmd`. cmd.exe re-parses the whole line before `%*` expands, so an argument containing `& ^ | " %VAR%` does not reach the task intact when the launcher is called from PowerShell.

`exe` writes a native `<task>.exe` instead, which receives its arguments unchanged from every shell. It is a copy of the mise-shim.exe that ships with the Windows build, so it can only be generated on Windows, and it adds ~220KB per task to a directory that is normally committed.

Default: cmd
Print help

Generate a tool stub for HTTP-based tools

This command generates tool stubs that can automatically download and execute tools from HTTP URLs. It can detect checksums, file sizes, and binary paths automatically by downloading and analyzing the tool.

When generating stubs with platform-specific URLs, the command will append new platforms to existing stub files rather than overwriting them. This allows you to incrementally build cross-platform tool stubs.

Usage: mise generate tool-stub [OPTIONS] <OUTPUT>

Options:

Binary path within the extracted archive

If not specified and the archive is downloaded, will auto-detect the most likely binary

Wrap stub in a bootstrap script that installs mise if not already present

When enabled, generates a bash script that: 1. Checks if mise is installed at the expected path 2. If not, downloads and installs mise using the embedded installer 3. Executes the tool stub using mise

Specify mise version for the bootstrap script

By default, uses the latest version from the install script. Use this to pin to a specific version (e.g., "2025.1.0").

Checksum algorithm to use when downloading artifacts

Accepts `blake3` or `sha256` and defaults to `blake3`. Cannot be used with `--lock` or `--skip-download` because those modes do not calculate checksums.

Default: blake3
Fetch checksums and sizes for an existing tool stub file

This reads an existing stub file and fills in any missing checksum/size fields by downloading the files. URLs must already be present in the stub.

HTTP backend type to use
Default: http
Resolve and embed lockfile data (exact version + platform URLs/checksums) into an existing stub file for reproducible installs without runtime API calls
Platform-specific binary paths in the format platform:path

Examples: --platform-bin windows-x64:tool.exe --platform-bin linux-x64:bin/tool

Platform-specific URLs in the format platform:url or just url (auto-detect platform)

When the output file already exists, new platforms will be appended to the existing platforms table. Existing platform URLs will be updated if specified again.

If only a URL is provided (without platform:), the platform will be automatically detected from the URL filename.

Examples: --platform-url linux-x64:https://... --platform-url https://nodejs.org/dist/v22.17.1/node-v22.17.1-darwin-arm64.tar.gz

Skip downloading for checksum and binary path detection (faster but less informative)
URL for downloading the tool

Example: https://github.com/owner/repo/releases/download/v2.0.0/tool-linux-x64.tar.gz

Version of the tool
Default: latest
Print help Arguments:
<OUTPUT>
Output file path for the tool stub

Removes mise CLI and all related data

Skips config directory by default.

Usage: mise implode [OPTIONS]

Options:

List directories that would be removed without actually removing them
Also remove config directory
Print help

Edit mise.toml interactively

Usage: mise edit [OPTIONS] [<PATH>]

Options:

Edit the global config file (~/.config/mise/config.toml)
Show what would be generated without writing to file
Path to a .tool-versions file to import tools from
Print help Arguments:
<PATH>
Path to the config file to create

Install a tool version

Installs a tool version to `~/.local/share/mise/installs/<TOOL>/<VERSION>` Installing alone will not activate the tools so they won't be in PATH. To install and/or activate in one command, use `mise use` which will create a `mise.toml` file in the current directory to activate this tool when inside the directory. Alternatively, run `mise exec <TOOL>@<VERSION> -- <COMMAND>` to execute a tool without creating config files.

Tools will be installed in parallel. To disable, set `--jobs=1` or `MISE_JOBS=1`

Usage: mise install [OPTIONS] [<TOOL@VERSION>] ...

Options:

Force reinstall even if already installed With no tools specified, reinstall all configured tools
Number of jobs to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_JOBS
Show what would be installed without actually installing
Show installation output

This argument will print backend output such as download, configuration, and compilation output.

Like --dry-run but exits with code 1 if there are tools to install

This is useful for scripts to check if tools need to be installed.

Also install tools required by tasks in the current scope

This prepares task tools without running task commands or dependencies. Combine with --monorepo to include tasks from every configured root.

Also install tools configured with `lazy = true`

By default, a bare `mise install` leaves lazy tools for first-command installation.

Only install versions released before this date or older than this duration

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y".

Install tools from every [monorepo].config_roots config root

Uses the active MISE_ENV and requires monorepo_root = true plus explicit [monorepo].config_roots in the monorepo root config.

Environment: MISE_MONOREPO
Connect backend install command stdin/stdout/stderr directly to the terminal Implies --jobs=1
Install tool(s) to a shared directory

Installs to the specified directory instead of the default install location. May require elevated permissions depending on the path.

Install tool(s) to the system-wide shared directory

Installs to /usr/local/share/mise/installs (or MISE_SYSTEM_DATA_DIR/installs). May require elevated permissions (e.g. sudo).

Print help Arguments:
<TOOL@VERSION>
Tool(s) to install e.g.: node@20

Install a tool version to a specific path

Used for building a tool to a directory for use outside of mise

Usage: mise install-into [OPTIONS] <TOOL@VERSION> <PATH>

Options:

Print help Arguments:
<TOOL@VERSION>
Tool to install e.g.: node@20
<PATH>
Path to install the tool into

Gets the latest available version for a plugin

Supports prefixes such as `node@20` to get the latest version of node 20.

Usage: mise latest [OPTIONS] <TOOL@VERSION> [<ASDF_VERSION>]

Options:

Show latest installed instead of available version
Only consider versions released before this date or older than this duration

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y". Overrides per-tool `minimum_release_age` options and the global `minimum_release_age` setting.

Print help Arguments:
<TOOL@VERSION>
Tool to get the latest version of
<ASDF_VERSION>
The version prefix to use when querying the latest version same as the first argument after the "@" used for asdf compatibility

Symlinks a tool version into mise

Use this for adding installs either custom compiled outside mise or built with a different tool.

Usage: mise link [OPTIONS] <TOOL@VERSION> <PATH>

Options:

Overwrite an existing tool version if it exists
Print help Arguments:
<TOOL@VERSION>
Tool name and version to create a symlink for
<PATH>
The local path to the tool version e.g.: ~/.nvm/versions/node/v20.0.0

Update lockfile checksums and URLs for all specified platforms

Updates checksums and download URLs for all platforms already specified in the lockfile. If no lockfile exists, shows what would be created based on the current configuration, including tools declared by tasks. This allows you to refresh lockfile data for platforms other than the one you're currently on. Operates on the lockfile in the current config root. Use TOOL arguments to target specific tools.

Usage: mise lock [OPTIONS] [<TOOL>] ...

Options:

Target only global config lockfiles (~/.config/mise/mise.lock and system config) By default, only the active project config root is locked
Number of jobs to run in parallel Values below 1 are treated as 1
Environment: MISE_JOBS
Show what would be updated without making changes
Comma-separated list of platforms to target e.g.: linux-x64,macos-arm64,windows-x64 If not specified, all platforms already in lockfile will be updated
Re-resolve fuzzy version selectors against the latest available versions

By default, `mise lock` refreshes metadata for the currently locked versions. With this flag, selectors like "latest", "lts", or prefixes like "20" are re-resolved against the latest matching remote versions, so the lockfile advances without installing anything. Config files are never modified: exactly pinned versions resolve to themselves and stay unchanged (use `mise upgrade --bump` to rewrite pins in mise.toml).

Output version changes as JSON

Prints an array of objects describing lockfile version changes: name, backend, lockfile, old_versions, new_versions. Version lists keep config/lockfile order; they are not sorted. Only version-level changes are reported: checksum/URL refreshes for unchanged versions produce no entries, so plain `mise lock --json` typically prints `[]` while still updating the lockfile. Suppresses the human-readable output. Combine with `--dry-run` to detect available updates without writing the lockfile.

Update mise.local.lock instead of mise.lock Use for tools defined in .local.toml configs
Only lock versions released before this age or date

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y". This only affects fuzzy version matches like "20" or "latest". Explicitly pinned versions like "22.5.0" are not filtered. Existing matching lockfile entries are preserved and are not downgraded solely by this flag.

Upgrade legacy lockfiles to the latest format

Existing unversioned lockfiles use format version 0 and are otherwise preserved to avoid unexpected lockfile drift. This flag upgrades them to the latest format with request-specific version bindings. Format upgrades always process every configured tool and cannot be combined with tool arguments.

Print help Arguments:
<TOOL>
Tool(s) to update in lockfile e.g.: node python If not specified, all configured and task-specific tools will be updated

List installed and active tool versions

This command lists tools that mise "knows about". These may be tools that are currently installed, or those that are in a config file (active) but may or may not be installed.

It's a useful command to get the current state of your tools.

Usage: mise ls [OPTIONS] [<INSTALLED_TOOL>] ...

Options:

Only show tool versions currently specified in a mise.toml
Only show tool versions currently specified in the global mise.toml
Only show tool versions that are installed (Hides tools defined in mise.toml but not installed)
Output in JSON format
Only show tool versions currently specified in the local mise.toml
Display missing tool versions
Don't fetch information such as outdated versions
Display all tracked config sources for tools
List tools from every [monorepo].config_roots config root

Uses the active MISE_ENV and requires monorepo_root = true plus explicit [monorepo].config_roots in the monorepo root config.

Environment: MISE_MONOREPO
Don't display headers
Display whether a version is outdated
Display versions matching this prefix
List only tools that can be pruned with `mise prune`
Print help Arguments:
<INSTALLED_TOOL>
Only show tool versions from [TOOL]

List runtime versions available for install.

Note that the results may be cached, run `mise cache clean` to clear the cache and get fresh results.

Usage: mise ls-remote [OPTIONS] [<TOOL@VERSION>] [<PREFIX>]

Options:

Show all installed plugins and versions
Only show versions released before this age or date

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y".

Output in JSON format (includes version metadata like created_at timestamps when available)
Disable checking the mise-versions host
Include pre-release versions in the output for backends that report upstream prerelease metadata or opt in to regex-based prerelease detection. Equivalent to setting `MISE_PRERELEASES=1` or the `prereleases` setting for the duration of this command.
Fail if release metadata fetches fail

Requires --json and --no-versions-host.

This prevents metadata consumers from accepting empty fallback results when a backend's metadata-producing upstream request fails.

Print help Arguments:
<TOOL@VERSION>
Tool to get versions for
<PREFIX>
The version prefix to use when querying the latest version same as the first argument after the "@"

Run Model Context Protocol (MCP) server

This command starts an MCP server that exposes mise functionality to AI assistants over stdin/stdout using JSON-RPC protocol.

The MCP server provides access to: - Installed and available tools - Task definitions and execution - Environment variables - Configuration information - Task execution via the run_task tool

Resources available: - mise://tools - List all tools (use ?include_inactive=true to include inactive tools) - mise://tasks - List all tasks with their configurations - mise://env - List all environment variables - mise://config - Show configuration files and project root

Tools available: - list_commands - Every mise command, with its declared effect on the world - install_tool - Install a tool with an optional version (not yet implemented) - run_task - Execute a mise task with optional arguments

Note: This is primarily intended for integration with AI assistants like Claude, Cursor, or other tools that support the Model Context Protocol.

Usage: mise mcp [OPTIONS]

Options:

Print help

[experimental] Build OCI container images from a mise.toml

Each tool becomes its own OCI layer, so bumping any single tool version only invalidates one content-addressable blob — unlike a Dockerfile where changing an early `RUN` invalidates every layer above it.

This command is experimental and requires `mise settings experimental=true` (or `MISE_EXPERIMENTAL=1`). Behavior, flags, and output layout may change in future releases.

Usage: mise oci [OPTIONS] <COMMAND>

Options:

Print help

[experimental] Build an OCI image from the current mise.toml

Each tool version becomes its own content-addressable OCI layer. Bumping a tool version only invalidates that tool's layer — other tools, the base image, and config are reused unchanged. The output directory conforms to the OCI image-layout spec and can be consumed by `skopeo`, `crane`, or `podman load`.

Requires `mise settings experimental=true` (or `MISE_EXPERIMENTAL=1`).

Usage: mise oci build [OPTIONS]

Options:

Copy a host file, directory, or symlink into the image (repeatable, HOST:IMAGE)
Output directory for the OCI image layout
Default: ./mise-oci
Base image reference (overrides [oci].from and the oci.default_from setting)
Also include tools from the global / system config (default: project-only)

By default `mise oci build` only packages tools declared in the project's mise config (and any parent configs at-or-below the project root, e.g. a monorepo root config). Personal dev tools in `~/.config/mise/config.toml` are excluded so they don't bake into a project image. Pass `--include-global` to revert to the old "merge all loaded configs" behavior.

Tag to record in the image index (the org.opencontainers.image.ref.name annotation)
Where to place tool installs inside the image (default: /mise)
Do not embed the currently-running mise binary at /usr/local/bin/mise
UID[:GID] to assign to every tar entry in generated layers

Overrides [oci].user_id / [oci].group_id. Defaults to 0:0. If GID is omitted, it defaults to UID. This affects file ownership only; [oci].user controls the image USER directive.

Print help

[experimental] Build an OCI image and push it to a registry

Pushes with mise's built-in registry client — no skopeo/crane/docker required. If `--image-dir` is not passed, builds fresh from the current mise.toml first. Only blobs the registry doesn't already have are uploaded, so repeat pushes of mostly-unchanged toolsets are cheap.

Tool layers whose tool, version, mount point, and file owner match the previously pushed image (or `--cache-from`) are reused without being rebuilt — those tools don't even need to be installed locally. Pass `--no-cache` to force a full local rebuild.

Credentials are read from the same places docker and podman use: `$REGISTRY_AUTH_FILE`, `$XDG_RUNTIME_DIR/containers/auth.json`, `~/.config/containers/auth.json`, and `~/.docker/config.json` (including credential helpers) — so `docker login` / `podman login` is all the setup needed.

Requires `mise settings experimental=true` (or `MISE_EXPERIMENTAL=1`).

Usage: mise oci push [OPTIONS] <REF>

Options:

Reuse unchanged tool layers from this image instead of the destination ref

Must live in the same repository as the destination. Useful when each push gets a unique tag (e.g. per-commit tags in CI): `--cache-from ghcr.io/me/dev:latest ghcr.io/me/dev:$SHA`.

Base image for the build (ignored with --image-dir)
Push an already-built OCI image layout (skip the build step)
Also include tools from the global / system config (default: project-only)

See `mise oci build --help` for details.

Override in-image mount point (ignored with --image-dir)
Don't reuse tool layers from the previously pushed image
Don't embed the mise binary (ignored with --image-dir)
UID[:GID] to assign to every tar entry when building (conflicts with --image-dir)

Overrides [oci].user_id / [oci].group_id. Defaults to 0:0. If GID is omitted, it defaults to UID. This affects file ownership only; [oci].user controls the image USER directive.

Maintain the tag as a multi-arch image index

Pushes this build's manifest by digest and points the tag at an OCI image index containing one entry per platform, preserving entries other architectures pushed. Run `mise oci push --update-index` from one runner per platform to assemble a multi-arch tag.

Print help Arguments:
<REF>
Destination registry reference (e.g. `ghcr.io/me/devenv:latest`)

[experimental] Build an OCI image from the current mise.toml and run a command in it

Equivalent to `mise oci build` followed by `docker run` / `podman run`. The built image is loaded into the local container engine (podman pulls the OCI layout natively; docker receives it via `docker load`) and the given command is executed inside it with stdin/stdout/stderr inherited.

Requires `mise settings experimental=true` (or `MISE_EXPERIMENTAL=1`) and one of: `podman`, `docker`.

Usage: mise oci run [OPTIONS] [<CMD>] ...

Options:

Container engine to use (`auto`, `podman`, or `docker`)
Default: auto
Base image reference for the build (ignored with --image-dir)
Use an already-built OCI image layout instead of building fresh
Also include tools from the global / system config (default: project-only)

See `mise oci build --help` for details.

Keep the loaded image in the engine's storage after the run

By default, both the container (`--rm`) and the loaded image are removed when the command exits, so repeated `mise oci run` calls don't accumulate images in podman / docker storage. Pass `--keep` to retain the image under the tag mise used (`mise-oci:run-*` for docker; the pulled image ID for podman).

Override in-image mount point (ignored with --image-dir)
Don't embed the mise binary (ignored with --image-dir)
UID[:GID] to assign to every tar entry when building (conflicts with --image-dir)

Overrides [oci].user_id / [oci].group_id. Defaults to 0:0. If GID is omitted, it defaults to UID. This affects file ownership only; [oci].user controls the image USER directive.

Bind-mount a host path (repeatable, `HOST:CONTAINER[:MODE]`)

Note: unlike `docker run -v`, there's no `-v` short flag here because mise reserves `-v` for --verbose. Use `--volume` or `--mount`.

Set environment variable in the container (repeatable, `KEY=VAL`)
Run interactively (pass `-i` to the engine)
Allocate a TTY (pass `-t` to the engine)
Working directory inside the container
Print help Arguments:
<CMD>
Command and arguments to run inside the container (after `--`)

Shows outdated tool versions

See `mise upgrade` to upgrade these versions.

Usage: mise outdated [OPTIONS] [<TOOL@VERSION>] ...

Options:

Compares against the latest versions available, not what matches the current config

For example, if you have `node = "20"` in your config by default `mise outdated` will only show other 20.x versions, not 21.x or 22.x versions.

Using this flag, if there are 21.x or newer versions it will display those instead of 20.x.

Output in JSON format
Deprecated shorthand for --bump
Show outdated tools including installed-but-inactive tools not present in the current config

By default, `mise outdated` only shows tools that come from the current config.

Only show outdated tools defined in local config files

This will only show tools that are defined in project-local mise.toml and will skip tools defined in the global config (~/.config/mise/config.toml).

Placeholder for future monorepo outdated checks; `mise outdated --monorepo` is not implemented yet.
Don't show table header
Print help Arguments:
<TOOL@VERSION>
Tool(s) to show outdated versions for e.g.: node@20 python@3.10 If not specified, all tools in global and local configs will be shown

Show the individuals supporting mise as Patron-tier members

Lists the individuals on the Patron tier from https://jdx.dev/patrons.json. The list refreshes daily; supporting terminals will render each patron's name as a clickable link via OSC 8 hyperlinks.

To appear here, become a patron at https://jdx.dev/sponsors.html.

Usage: mise patrons [OPTIONS]

Options:

Output in JSON format
Bypass the local cache and re-fetch
Print help

Manage plugins

Usage: mise plugins [OPTIONS] [COMMAND]

Options:

list all available remote plugins

same as `mise plugins ls-remote`

The built-in plugins only Normally these are not shown
Show the git url for each plugin e.g.: https://github.com/mise-plugins/vfox-cmake.git
Show the git refs for each plugin e.g.: main 1234abc
List installed plugins

This is the default behavior but can be used with --core to show core and user plugins

Print help

Install a plugin

note that mise can automatically install plugins when you install a tool e.g.: `mise install cmake@3.30` will autoinstall the cmake plugin

This behavior can be modified in ~/.config/mise/config.toml

Usage: mise plugins install [OPTIONS] [<NEW_PLUGIN>] [<GIT_URL>] [<REST>] ...

Options:

Install all missing plugins This will only install plugins that have matching shorthands. i.e.: they don't need the full git repo url
Reinstall even if plugin exists
Number of jobs to run in parallel Values below 1 are treated as 1
Show installation output
Print help Arguments:
<NEW_PLUGIN>
The name of the plugin to install e.g.: cmake, poetry Can specify multiple plugins: `mise plugins install cmake poetry`
<GIT_URL>
The git url of the plugin

Symlinks a plugin into mise

This is used for developing a plugin.

Usage: mise plugins link [OPTIONS] <NAME> [<DIR>]

Options:

Overwrite existing plugin
Print help Arguments:
<NAME>
The name of the plugin e.g.: cmake, poetry
<DIR>
The local path to the plugin e.g.: ./vfox-cmake

List installed plugins

Can also show remotely available plugins to install.

Usage: mise plugins ls [OPTIONS]

Options:

List all available remote plugins Same as `mise plugins ls-remote`
The built-in plugins only Normally these are not shown
Show plugins with available updates Checks the remote for newer versions and only displays plugins that are outdated
Show the git url for each plugin e.g.: https://github.com/mise-plugins/vfox-cmake.git
Show the git refs for each plugin e.g.: main 1234abc
List installed plugins
Print help

List all available remote plugins

The full list is here: https://github.com/jdx/mise/blob/main/registry/

Examples:


$ mise plugins ls-remote

Usage: mise plugins ls-remote [OPTIONS]

Options:

Show the git url for each plugin e.g.: https://github.com/mise-plugins/mise-poetry.git
Only show the name of each plugin by default it will show a "*" next to installed plugins
Print help

Removes a plugin

Usage: mise plugins uninstall [OPTIONS] [<PLUGIN>] ...

Options:

Remove all plugins
Also remove the plugin's installs, downloads, and cache
Print help Arguments:
<PLUGIN>
Plugin(s) to remove

Updates a plugin to the latest version

note: this updates the plugin itself, not the runtime versions

Usage: mise plugins update [OPTIONS] [<PLUGIN>] ...

Options:

Number of jobs to run in parallel Values below 1 are treated as 1 Default: 4
Print help Arguments:
<PLUGIN>
Plugin(s) to update

[experimental] Manage project dependencies

Runs all applicable dependency install steps for the current project. This checks if dependency lockfiles are newer than installed outputs (e.g., package-lock.json vs node_modules/) and runs install commands if needed.

Providers with `auto = true` are automatically invoked before `mise x` and `mise run` unless skipped with the --no-deps flag.

Usage: mise deps [OPTIONS] [<PROVIDER>] [COMMAND]

Options:

Show why a provider is fresh or stale (requires a provider argument)
Force run all deps steps even if outputs are fresh
Only check if deps install is needed, don't run commands
Show what deps providers are available
Install dependencies from every [monorepo].config_roots config root

Requires monorepo_root = true plus explicit [monorepo].config_roots in the monorepo root config. Providers are named like //apps/api:uv.

Environment: MISE_MONOREPO
Run specific deps rule(s) only
Skip specific deps rule(s)
Print help Arguments:
<PROVIDER>
Provider to operate on (runs only this provider, or use with --explain)

Add a dependency

Adds one or more packages to the project using the appropriate package manager. Package specs use the format `ecosystem:package`, e.g., `npm:react` or `npm:@types/react@19`.

Usage: mise deps add [OPTIONS] <PACKAGES> ...

Options:

Add as a development dependency
Print help Arguments:
<PACKAGES>
Package(s) to add (e.g., npm:react, npm:@types/react@19)

Install all project dependencies

Checks if dependency lockfiles are newer than installed outputs and runs install commands if needed.

Usage: mise deps install [OPTIONS] [<PROVIDER>]

Options:

Show why a provider is fresh or stale (requires a provider argument)
Force run all deps steps even if outputs are fresh
Only check if deps install is needed, don't run commands
Show what deps providers are available
Install dependencies from every [monorepo].config_roots config root

Requires monorepo_root = true plus explicit [monorepo].config_roots in the monorepo root config. Providers are named like //apps/api:uv.

Environment: MISE_MONOREPO
Run specific deps rule(s) only
Skip specific deps rule(s)
Print help Arguments:
<PROVIDER>
Provider to operate on (runs only this provider, or use with --explain)

Remove a dependency

Removes one or more packages from the project using the appropriate package manager. Package specs use the format `ecosystem:package`, e.g., `npm:lodash`.

Usage: mise deps remove [OPTIONS] <PACKAGES> ...

Options:

Print help Arguments:
<PACKAGES>
Package(s) to remove (e.g., npm:lodash)

Delete unused versions of tools

mise tracks which config files have been used in ~/.local/state/mise/tracked-configs Versions which are no longer the latest specified in any of those configs are deleted. Versions installed only with environment variables `MISE_<TOOL>_VERSION` will be deleted, as will versions only referenced on the command line `mise exec <TOOL>@<VERSION>`.

Tool stubs that have been executed are tracked in ~/.local/state/mise/tracked-stubs. Versions still referenced by a tracked stub are not deleted.

You can list prunable tools with `mise ls --prunable`

Usage: mise prune [OPTIONS] [<INSTALLED_TOOL>] ...

Options:

Do not actually delete anything
Prune only tracked and trusted configuration links that point to nonexistent configurations
Like --dry-run but exits with code 1 if there are tools to prune

This is useful for scripts to check if tools need to be pruned.

Placeholder for future monorepo pruning; `mise prune --monorepo` is not implemented yet.
Prune only unused versions of tools
Print help Arguments:
<INSTALLED_TOOL>
Prune only these tools

List available tools to install

This command lists the tools available in the registry as shorthand names.

For example, `poetry` is shorthand for `asdf:mise-plugins/mise-poetry`.

Usage: mise registry [OPTIONS] [<NAME>]

Options:

Show only tools for this backend
Print all tools with descriptions for shell completions
Hide aliased tools
Output in JSON format
Include security features for each tool's backends in JSON output.

Requires --json. Security info is de-duplicated across all of a tool's backends. This can add noticeable time for large listings since each backend's security info is resolved individually.

Print help Arguments:
<NAME>
Show only the specified tool's full name

Creates new shims based on bin paths from currently installed tools.

This creates new shims in the configured user shim directory for CLIs that have been added. With `--system`, it rebuilds the configured system shim farm instead. mise will try to do this automatically for commands like `npm i -g` but there are other ways to install things (like using yarn or pnpm for node) that mise does not know about and so it will be necessary to call this explicitly.

If you think mise should automatically call this for a particular command, please open an issue on the mise repo. You can also set up a shell function to reshim automatically (it's really fast so you don't need to worry about overhead):


npm() {
command npm "$@"
mise reshim
}

Note that this creates shims for _all_ installed tools, not just the ones that are currently active in mise.toml.

Usage: mise reshim [OPTIONS] [<TOOL>] [<VERSION>]

Options:

Rebuilds all mise-owned shims
Rebuild the system shim farm
Print help

Run task(s)

This command will run a task, or multiple tasks in parallel. Tasks may have dependencies on other tasks or on source files. If source is configured on a task, it will only run if the source files have changed.

Tasks can be defined in mise.toml or as standalone scripts. In mise.toml, tasks take this form:


[tasks.build]
run = "npm run build"
sources = ["src/**/*.ts"]
outputs = ["dist/**/*.js"]

Alternatively, tasks can be defined as standalone scripts. These must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or `.config/mise/tasks`. The name of the script will be the name of the tasks.


$ cat .mise/tasks/build<<EOF
#!/usr/bin/env bash
npm run build
EOF
$ mise run build

Usage: mise run [OPTIONS]

Options:

Run matching tasks only for projects affected by Git changes
Git base revision for --affected Defaults to MISE_AFFECTED_BASE, CI metadata, or HEAD~1
Explain why projects and tasks were selected by --affected
Git head revision for --affected Defaults to MISE_AFFECTED_HEAD, CI metadata, or HEAD
Output affected projects and tasks as JSON without running tasks
Open the interactive selector with all tasks from the entire monorepo
Continue running tasks even if one fails
Change to this directory before executing the command
Force the tasks to run even if outputs are up to date
Number of tasks to run in parallel Values below 1 are treated as 1 [default: 4] Configure with `jobs` config or `MISE_JOBS` env var
Environment: MISE_JOBS
Don't actually run the task(s), just print them in order of execution
Change how tasks information is output when running tasks

- `prefix` - Print stdout/stderr by line, prefixed with the task's label - `interleave` - Print directly to stdout/stderr instead of by line - `replacing` - Stdout is replaced each time, stderr is printed as is - `timed` - Only show stdout lines if they are displayed for more than 1 second - `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output - `quiet` - Don't show extra output - `silent` - Don't show any output including stdout and stderr from the task except for errors

Environment: MISE_TASK_OUTPUT
Don't show extra output
Environment: MISE_QUIET
Read/write directly to stdin/stdout/stderr instead of by line Redactions are not applied with this option Configure with `raw` config or `MISE_RAW` env var
Shell to use to run toml tasks

Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS` Or it can be overridden with the `shell` property on a task.

Don't show any output except for errors
Environment: MISE_SILENT
Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
Allow specific env var through (implies --deny-env for everything else) Supports wildcards, e.g. --allow-env='MYAPP_*'
Allow network to specific host (implies --deny-net for everything else)
Allow reads from specific path (implies --deny-read for everything else)
Allow writes to specific path (implies --deny-write for everything else)
Block reads, writes, network, and env vars
Block env var inheritance (only PATH, HOME, USER, SHELL, TERM, LANG pass through)
Block all network access
Block filesystem reads (system libs and tool dirs still accessible)
Block all filesystem writes
Bypass the environment cache and recompute the environment
Do not use cache on remote tasks
Environment: MISE_TASK_REMOTE_NO_CACHE
Skip automatic dependency preparation
Hides elapsed time after each task completes

Default to always hide with `MISE_TASK_TIMINGS=0`

Run only the specified tasks skipping all dependencies
Environment: MISE_TASK_SKIP_DEPENDS
Skip installing tools before running tasks

Can also be set persistently with the `task.run_auto_install` setting or `MISE_TASK_RUN_AUTO_INSTALL=false` env var

Set task output cache access for this run

- `read-write` - Read cached results and write new results - `read-only` - Read cached results without writing new results - `write-only` - Write new results without reading cached results - `off` - Disable task output caching - `local-only` - Read and write only the local cache; currently equivalent to `read-write`

Default: read-write
Environment: MISE_TASK_CACHE
Explain the inputs that produced each task's output cache key
Output cache-key input details as JSON Lines without running tasks
Report task output cache hits, restored bytes, and time saved
Timeout for the task to complete e.g.: 30s, 5m
Shows elapsed time after each task completes

Default to always show with `MISE_TASK_TIMINGS=1`

Search for tools in the registry

This command searches a tool in the registry.

By default, it will show all tools that fuzzy match the search term. For non-fuzzy matches, use the `--match-type` flag.

Usage: mise search [OPTIONS] [<NAME>]

Options:

Show interactive search
Match type: equal, contains, or fuzzy
Default: fuzzy
Don't display headers
Print help Arguments:
<NAME>
The tool to search for

Updates mise itself.

Uses the GitHub Releases API to find the latest release and binary. By default, this will also update any installed plugins. Uses mise's GitHub token resolution chain for authenticated requests.

Packagers can disable this command so that mise is updated through the package manager instead. See https://mise.jdx.dev/contributing.html#packaging-and-self-update-instructions

Usage: mise self-update [OPTIONS] [<VERSION>]

Options:

Update even if already up to date
Skip confirmation prompt
Disable auto-updating plugins
Print help Arguments:
<VERSION>
Update to a specific version

Set environment variables in mise.toml

By default, this command modifies `mise.toml` in the current directory. If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`), the lowest precedence file (`mise.toml`) will be used. See https://mise.jdx.dev/configuration.html#target-file-for-write-operations

Use `-E <env>` to create/modify environment-specific config files like `mise.<env>.toml`.

Usage: mise set [OPTIONS] [<ENV_VAR>] ...

Options:

Create/modify an environment-specific config file like .mise.<env>.toml
Set the environment variable in the global config file
[experimental] Encrypt the value with age before storing
[experimental] Age identity file for encryption

Defaults to ~/.config/mise/age.txt if it exists

[experimental] Age recipient (x25519 public key) for encryption

Can be used multiple times. Requires --age-encrypt.

[experimental] SSH recipient (public key or path) for age encryption

Can be used multiple times. Requires --age-encrypt.

Render completions
The TOML file to update

Can be a file path or directory. If a directory is provided, will create/use mise.toml in that directory. Defaults to [`MISE_DEFAULT_CONFIG_FILENAME`](https://mise.jdx.dev/configuration.html#mise_default_config_filename) environment variable, or `mise.toml`. Use [`MISE_GLOBAL_CONFIG_FILE`](https://mise.jdx.dev/configuration.html#mise_global_config_file) to choose a different global config path.

Show raw values instead of redacting secrets
Prompt for environment variable values
Remove the environment variable from config file

Can be used multiple times.

Read the value from stdin (for multiline input)

When using --stdin, provide a single key without a value. The value will be read from stdin until EOF.

Print help Arguments:
<ENV_VAR>
Environment variable(s) to set e.g.: NODE_ENV=production

Manage settings

Usage: mise settings [OPTIONS] [<SETTING>] [<VALUE>] [COMMAND]

Options:

List all settings
Output in JSON format
Use the local config file instead of the global one
Output in TOML format
Print all settings with descriptions for shell completions
Output in JSON format with sources
Print help Arguments:
<SETTING>
Name of setting
<VALUE>
Setting value to set

Adds a setting to the configuration file

Used with an array setting, this will append the value to the array. This modifies the contents of ~/.config/mise/config.toml

Usage: mise settings add [OPTIONS] <SETTING> [<VALUE>]

Options:

Use the local config file instead of the global one
Print help Arguments:
<SETTING>
The setting to set
<VALUE>
The value to set (optional if provided as KEY=VALUE)

Show a current setting

This is the contents of a single entry in ~/.config/mise/config.toml

Note that aliases are also stored in this file but managed separately with `mise tool-alias get`

Usage: mise settings get [OPTIONS] <SETTING>

Options:

Use the local config file instead of the global one
Print help Arguments:
<SETTING>
The setting to show

Show current settings

This is the contents of ~/.config/mise/config.toml

Note that aliases are also stored in this file but managed separately with `mise tool-alias`

Usage: mise settings ls [OPTIONS] [<SETTING>]

Options:

List all settings
Output in JSON format
Use the local config file instead of the global one
Output in TOML format
Print all settings with descriptions for shell completions
Output in JSON format with sources
Print help Arguments:
<SETTING>
Name of setting

Add/update a setting

This modifies the contents of ~/.config/mise/config.toml by default. With `--local`, modifies the local config file instead. See https://mise.jdx.dev/configuration.html#target-file-for-write-operations

Usage: mise settings set [OPTIONS] <SETTING> [<VALUE>]

Options:

Use the local config file instead of the global one
Print help Arguments:
<SETTING>
The setting to set
<VALUE>
The value to set (optional if provided as KEY=VALUE)

Clears a setting

This modifies the contents of ~/.config/mise/config.toml

Usage: mise settings unset [OPTIONS] <KEY>

Options:

Use the local config file instead of the global one
Print help Arguments:
<KEY>
The setting to remove

Sets a tool version for the current session.

Only works in a session where mise is already activated.

This works by setting environment variables for the current shell session such as `MISE_NODE_VERSION=20` which is "eval"ed as a shell function created by `mise activate`.

Usage: mise shell [OPTIONS] <TOOL@VERSION> ...

Options:

Number of jobs to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_JOBS
Removes a previously set version
Connect backend install command stdin/stdout/stderr directly to the terminal Implies --jobs=1
Print help Arguments:
<TOOL@VERSION>
Tool(s) to use

Manage shell aliases.

Usage: mise shell-alias [OPTIONS] [COMMAND]

Options:

Don't show table header
Print help

Show the command for a shell alias

Usage: mise shell-alias get [OPTIONS] <shell_alias>

Options:

Print help Arguments:
<shell_alias>
The alias to show

List shell aliases

Shows the shell aliases that are set in the current directory. These are defined in `mise.toml` under the `[shell_alias]` section.

Usage: mise shell-alias ls [OPTIONS]

Options:

Don't show table header
Print help

Add/update a shell alias

This modifies the contents of ~/.config/mise/config.toml

Usage: mise shell-alias set [OPTIONS] <shell_alias> [<COMMAND>]

Options:

Print help Arguments:
<shell_alias>
The alias name
<COMMAND>
The command to run (optional if provided as ALIAS=COMMAND)

Removes a shell alias

This modifies the contents of ~/.config/mise/config.toml

Usage: mise shell-alias unset [OPTIONS] <shell_alias>

Options:

Print help Arguments:
<shell_alias>
The alias to remove

Show the companies sponsoring mise and the jdx.dev open source tools

Usage: mise sponsors [OPTIONS]

Options:

Print help

Synchronize tools from other version managers with mise

Usage: mise sync [OPTIONS] <COMMAND>

Options:

Print help

Symlinks all tool versions from an external tool into mise

For example, use this to import all Homebrew node installs into mise

This won't overwrite managed installs, runtime aliases, or links from other providers.

Usage: mise sync node [OPTIONS]

Options:

Get tool versions from Homebrew
Get tool versions from nodenv
Get tool versions from nvm
Print help

Symlinks all tool versions from an external tool into mise

For example, use this to import all pyenv installs into mise

This won't overwrite managed installs, runtime aliases, or links from other providers.

Usage: mise sync python [OPTIONS]

Options:

Get tool versions from pyenv
Sync tool versions with uv (2-way sync)
Print help

Symlinks all ruby tool versions from an external tool into mise

Usage: mise sync ruby [OPTIONS]

Options:

Get tool versions from Homebrew
Print help

Manage tasks

Usage: mise tasks [OPTIONS] [<TASK>] [COMMAND]

Options:

Only show global tasks
Output in JSON format
Only show non-global tasks
Show all columns
Load all tasks from the entire monorepo, including sibling directories. By default, only tasks from the current directory hierarchy are loaded.
Display tasks for usage completion
Show hidden tasks
Only show task names, one per line. Useful for piping to fzf and similar tools.
Do not print table header
Sort by column. Default is name.
Sort order. Default is asc.
Print help Arguments:
<TASK>
Task name to get info of

Create a new task

Adds a task to the local mise.toml file. See https://mise.jdx.dev/configuration.html#target-file-for-write-operations

Usage: mise tasks add [OPTIONS] <TASK> [<RUN>] ...

Options:

Other names for the task
Add dependencies to the task
Run the task in a specific directory
Create a file task instead of a toml task
Hide the task from `mise tasks` and completions
Do not print the command before running
Directly connect stdin/stdout/stderr
Glob patterns of files this task uses as input
Wait for these tasks to complete if they are to run
Dependencies to run after the task runs
Description of the task
Glob patterns of files this task creates, to skip if they are not modified
Command to run on windows
Run the task in a specific shell
Do not print the command or its output
Print help Arguments:
<TASK>
Tasks name to add

Display a tree visualization of a dependency graph

The graph is built from declared dependencies: `depends`, `depends_post`, and `wait_for`. Task references inside a `run` or `run_windows` array (`{ task = "..." }` or `{ tasks = [...] }`) are execution steps, not graph edges, so they do not appear here. Those nested tasks still run, including their own `depends`.

Usage: mise tasks deps [OPTIONS] [<TASKS>] ...

Options:

Collapse repeated dependencies after their first occurrence
Display dependencies in DOT format
Show hidden tasks
Print help Arguments:
<TASKS>
Tasks to show dependencies for Can specify multiple tasks by separating with spaces e.g.: mise tasks deps lint test check

Edit a task with $EDITOR

The task will be created as a standalone script if it does not already exist.

Usage: mise tasks edit [OPTIONS] <TASK>

Options:

Display the path to the task instead of editing it
Print help Arguments:
<TASK>
Task to edit

[experimental] Inspect the workspace project graph

Usage: mise tasks graph [OPTIONS]

Options:

Output the project graph as JSON
Explain provider attribution for inferred projects and tasks
Do not print table headers
Print help

Get information about a task

Usage: mise tasks info [OPTIONS] <TASK>

Options:

Output in JSON format
Print help Arguments:
<TASK>
Name of the task to get information about

List available tasks to execute These may be included from the config file or from the project's .mise/tasks directory mise will merge all tasks from all parent directories into this list.

So if you have global tasks in `~/.config/mise/tasks/*` and project-specific tasks in ~/myproject/.mise/tasks/*, then they'll both be available but the project-specific tasks will override the global ones if they have the same name.

Usage: mise tasks ls [OPTIONS]

Options:

Only show global tasks
Output in JSON format
Only show non-global tasks
Show all columns
Load all tasks from the entire monorepo, including sibling directories. By default, only tasks from the current directory hierarchy are loaded.
Display tasks for usage completion
Show hidden tasks
Only show task names, one per line. Useful for piping to fzf and similar tools.
Do not print table header
Sort by column. Default is name.
Sort order. Default is asc.
Print help

Run task(s)

This command will run a task, or multiple tasks in parallel. Tasks may have dependencies on other tasks or on source files. If source is configured on a task, it will only run if the source files have changed.

Tasks can be defined in mise.toml or as standalone scripts. In mise.toml, tasks take this form:


[tasks.build]
run = "npm run build"
sources = ["src/**/*.ts"]
outputs = ["dist/**/*.js"]

Alternatively, tasks can be defined as standalone scripts. These must be located in `mise-tasks`, `.mise-tasks`, `.mise/tasks`, `mise/tasks` or `.config/mise/tasks`. The name of the script will be the name of the tasks.


$ cat .mise/tasks/build<<EOF
#!/usr/bin/env bash
npm run build
EOF
$ mise run build

Usage: mise tasks run [OPTIONS]

Options:

Run matching tasks only for projects affected by Git changes
Git base revision for --affected Defaults to MISE_AFFECTED_BASE, CI metadata, or HEAD~1
Explain why projects and tasks were selected by --affected
Git head revision for --affected Defaults to MISE_AFFECTED_HEAD, CI metadata, or HEAD
Output affected projects and tasks as JSON without running tasks
Open the interactive selector with all tasks from the entire monorepo
Continue running tasks even if one fails
Change to this directory before executing the command
Force the tasks to run even if outputs are up to date
Number of tasks to run in parallel Values below 1 are treated as 1 [default: 4] Configure with `jobs` config or `MISE_JOBS` env var
Environment: MISE_JOBS
Don't actually run the task(s), just print them in order of execution
Change how tasks information is output when running tasks

- `prefix` - Print stdout/stderr by line, prefixed with the task's label - `interleave` - Print directly to stdout/stderr instead of by line - `replacing` - Stdout is replaced each time, stderr is printed as is - `timed` - Only show stdout lines if they are displayed for more than 1 second - `keep-order` - Print stdout/stderr by line, prefixed with the task's label, but keep the order of the output - `quiet` - Don't show extra output - `silent` - Don't show any output including stdout and stderr from the task except for errors

Environment: MISE_TASK_OUTPUT
Don't show extra output
Environment: MISE_QUIET
Read/write directly to stdin/stdout/stderr instead of by line Redactions are not applied with this option Configure with `raw` config or `MISE_RAW` env var
Shell to use to run toml tasks

Defaults to `sh -c -o errexit -o pipefail` on unix, and `cmd /c` on Windows Can also be set with the setting `MISE_UNIX_DEFAULT_INLINE_SHELL_ARGS` or `MISE_WINDOWS_DEFAULT_INLINE_SHELL_ARGS` Or it can be overridden with the `shell` property on a task.

Don't show any output except for errors
Environment: MISE_SILENT
Tool(s) to run in addition to what is in mise.toml files e.g.: node@20 python@3.10
Allow specific env var through (implies --deny-env for everything else) Supports wildcards, e.g. --allow-env='MYAPP_*'
Allow network to specific host (implies --deny-net for everything else)
Allow reads from specific path (implies --deny-read for everything else)
Allow writes to specific path (implies --deny-write for everything else)
Block reads, writes, network, and env vars
Block env var inheritance (only PATH, HOME, USER, SHELL, TERM, LANG pass through)
Block all network access
Block filesystem reads (system libs and tool dirs still accessible)
Block all filesystem writes
Bypass the environment cache and recompute the environment
Do not use cache on remote tasks
Environment: MISE_TASK_REMOTE_NO_CACHE
Skip automatic dependency preparation
Hides elapsed time after each task completes

Default to always hide with `MISE_TASK_TIMINGS=0`

Run only the specified tasks skipping all dependencies
Environment: MISE_TASK_SKIP_DEPENDS
Skip installing tools before running tasks

Can also be set persistently with the `task.run_auto_install` setting or `MISE_TASK_RUN_AUTO_INSTALL=false` env var

Set task output cache access for this run

- `read-write` - Read cached results and write new results - `read-only` - Read cached results without writing new results - `write-only` - Write new results without reading cached results - `off` - Disable task output caching - `local-only` - Read and write only the local cache; currently equivalent to `read-write`

Default: read-write
Environment: MISE_TASK_CACHE
Explain the inputs that produced each task's output cache key
Output cache-key input details as JSON Lines without running tasks
Report task output cache hits, restored bytes, and time saved
Timeout for the task to complete e.g.: 30s, 5m
Shows elapsed time after each task completes

Default to always show with `MISE_TASK_TIMINGS=1`

Validate tasks for common errors and issues

Usage: mise tasks validate [OPTIONS] [<TASKS>] ...

Options:

Only show errors (skip warnings)
Output validation results in JSON format
Print help Arguments:
<TASKS>
Tasks to validate If not specified, validates all tasks

Test a tool installs and executes

Usage: mise test-tool [OPTIONS] [<TOOLS>] ...

Options:

Test every tool specified in registry/
Number of tool tests to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_TEST_TOOL_JOBS
Test all tools specified in config files
Also test tools not defined in registry/, guessing how to test it
Connect backend install command stdin/stdout/stderr directly to the terminal Implies --jobs=1
Print help Arguments:
<TOOLS>
Tool(s) to test

Display git provider tokens mise will use

Usage: mise token [OPTIONS] <COMMAND>

Options:

Print help

Display the Forgejo token mise will use for a given host

Shows which token source mise would use, useful for debugging authentication issues. The token is masked by default.

Usage: mise token forgejo [OPTIONS] [<HOST>]

Options:

Show the full unmasked token
Print help Arguments:
<HOST>
Forgejo hostname
Default: codeberg.org

Display the GitHub token mise will use for a given host

Shows which token source mise would use, useful for debugging authentication issues. The token is masked by default.

Usage: mise token github [OPTIONS] [<HOST>]

Options:

Resolve only via the native GitHub OAuth source (cache, refresh, or device-code flow), bypassing other token sources
Print only the token value
Mint a fresh OAuth token even if the cached one has not expired, via the refresh-token grant or a new device-code flow. Use after changing the GitHub App's installations or permissions: cached tokens keep their original access until they expire
Show the full unmasked token
Print help Arguments:
<HOST>
GitHub hostname
Default: github.com

Display the GitLab token mise will use for a given host

Shows which token source mise would use, useful for debugging authentication issues. The token is masked by default.

Usage: mise token gitlab [OPTIONS] [<HOST>]

Options:

Show the full unmasked token
Print help Arguments:
<HOST>
GitLab hostname
Default: gitlab.com

Gets information about a tool

Usage: mise tool [OPTIONS] <TOOL>

Options:

Output in JSON format
Only show active versions
Only show backend field
Only show config source
Only show description field
Only show installed versions
Only show requested versions
Only show tool options
Print help Arguments:
<TOOL>
Tool name to get information about

Execute a tool stub

Tool stubs are executable files containing TOML configuration that specify which tool to run and how to run it. They provide a convenient way to create portable, self-contained executables that automatically manage tool installation and execution.

A tool stub consists of:

- A shebang line: #!/usr/bin/env -S mise tool-stub - TOML configuration specifying the tool, version, and options - Optional comments describing the tool's purpose

Example stub file:

```toml #!/usr/bin/env -S mise tool-stub # Node.js v20 development environment

tool = "node" version = "20.0.0" bin = "node" ```

The stub will automatically install the specified tool version if missing and execute it with any arguments passed to the stub.

For more information, see: https://mise.jdx.dev/dev-tools/tool-stubs.html

Usage: mise tool-stub <FILE> [<ARGS>] ...

Arguments:

<FILE>
Path to the TOML tool stub file to execute

The stub file must contain TOML configuration specifying the tool and version to run. At minimum, it should specify a 'version' field. Other common fields include 'tool', 'bin', and backend-specific options.

<ARGS>
Arguments to pass to the tool

All arguments after the stub file path will be forwarded to the underlying tool. Use '--' to separate mise arguments from tool arguments if needed.

Marks a config file as trusted

This means mise is allowed to parse the file when it needs to read config that may execute code or affect the environment. Without trust, mise may prompt, skip the config in some discovery paths, or fail with an untrusted-config error when it cannot prompt.

In normal mode, commands that execute project-defined behavior (`mise run`, naked task invocations such as `mise <TASK>`, `mise install`, `mise exec`, and `mise watch`) automatically trust their active config. Paranoid mode requires explicit, content-bound trust for every non-global config.

In normal mode, safe config files do not require trust: files that only contain `min_version`, `[tools]` entries with plain version strings (or arrays of them), and `[tasks]` without templates or tool options.

Trust is shared across git worktrees: a config file inside a linked worktree is trusted when the equivalent path in the repository's main checkout has been trusted. Paranoid mode disables this sharing since worktrees can check out branches with different config contents.

Usage: mise trust [OPTIONS] [<CONFIG_FILE>]

Options:

Trust all config files in the current directory, its parents, and its subdirectories

Subdirectories are walked respecting .gitignore, skipping hidden directories and common build/dependency directories (node_modules, vendor, target, dist, build).

Do not trust this config and ignore it in the future
Show the trusted status of config files from the current directory and its parents. Does not trust or untrust any files.
Remove explicit trust for this config
Print help Arguments:
<CONFIG_FILE>
The config file whose trust status to change

Removes installed tool versions

This only removes the installed version, it does not modify mise.toml.

Usage: mise uninstall [OPTIONS] [<INSTALLED_TOOL@VERSION>] ...

Options:

Delete all installed versions
Do not actually delete anything
Like --dry-run but exits with code 1 if there are tools to uninstall

This is useful for scripts to check if tools need to be uninstalled.

Print help Arguments:
<INSTALLED_TOOL@VERSION>
Tool(s) to remove

Remove environment variable(s) from the config file.

By default, this command modifies `mise.toml` in the current directory.

Usage: mise unset [OPTIONS] [<ENV_KEY>] ...

Options:

Specify a file to use instead of `mise.toml`

Can be a file path or directory. If a directory is provided, will create/use mise.toml in that directory.

Defaults to [`MISE_DEFAULT_CONFIG_FILENAME`](https://mise.jdx.dev/configuration.html#mise_default_config_filename) environment variable, or `mise.toml`. Use [`MISE_GLOBAL_CONFIG_FILE`](https://mise.jdx.dev/configuration.html#mise_global_config_file) to choose a different global config path.

Use the global config file
Print help Arguments:
<ENV_KEY>
Environment variable(s) to remove e.g.: NODE_ENV

Remove explicit trust for a config

Usage: mise untrust [OPTIONS] [<CONFIG_FILE>]

Options:

Print help Arguments:
<CONFIG_FILE>
The config file to untrust

Removes installed tool versions from mise.toml

By default, this will use the `mise.toml` file that has the tool defined. If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`), the lowest precedence file (`mise.toml`) will be used. See https://mise.jdx.dev/configuration.html#target-file-for-write-operations

In the following order:
- If `--global` is set, it will use the global config file.
- If `--path` is set, it will use the config file at the given path.
- If `--env` is set, it will use `mise.<env>.toml`.
- If [`MISE_DEFAULT_CONFIG_FILENAME`](https://mise.jdx.dev/configuration.html#mise_default_config_filename) is set, it will use that instead.
- If `MISE_OVERRIDE_CONFIG_FILENAMES` is set, it will the first from that list.
- Otherwise just "mise.toml" or global config if cwd is home directory.

Use [`MISE_GLOBAL_CONFIG_FILE`](https://mise.jdx.dev/configuration.html#mise_global_config_file) to choose a different global config path.

Will also prune the installed version if no other configurations are using it.

Usage: mise unuse [OPTIONS] <INSTALLED_TOOL@VERSION> ...

Options:

Create/modify an environment-specific config file like .mise.<env>.toml
Use the global config file (`~/.config/mise/config.toml`) instead of the local one
Specify a path to a config file or directory

If a directory is specified, it will look for a config file in that directory following the rules above.

Do not also prune the installed version
Print help Arguments:
<INSTALLED_TOOL@VERSION>
Tool(s) to remove

Upgrades outdated tools

By default, this keeps the range specified in mise.toml. So if you have node@20 set, it will upgrade to the latest 20.x.x version available. See the `--bump` flag to use the latest version and bump the version in mise.toml.

This will update mise.lock if it is enabled, see https://mise.jdx.dev/configuration/settings.html#lockfile

Usage: mise upgrade [OPTIONS] [<INSTALLED_TOOL@VERSION>] ...

Options:

Upgrades to the latest version available, bumping the version in mise.toml

For example, if you have `node = "20.0.0"` in your mise.toml but 22.1.0 is the latest available, this will install 22.1.0 and set `node = "22.1.0"` in your config.

It keeps the same precision as what was there before, so if you instead had `node = "20"`, it would change your config to `node = "22"`.

Display multiselect menu to choose which tools to upgrade
Number of jobs to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_JOBS
Deprecated shorthand for --bump
Just print what would be done, don't actually do it
Tool(s) to exclude from upgrading e.g.: go python
Like --dry-run but exits with code 1 if there are outdated tools

This is useful for scripts to check if tools need to be upgraded.

Upgrade all tools, including installed-but-inactive tools not present in the current config
Only upgrade tools defined in local config files

This will only upgrade tools that are defined in project-local mise.toml and will skip tools defined in the global config (~/.config/mise/config.toml).

Only upgrade to versions released before this date or older than this duration

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y". This can be useful for reproducibility or security purposes.

This only affects fuzzy version matches like "20" or "latest". Explicitly pinned versions like "22.5.0" are not filtered.

Placeholder for future monorepo upgrades; `mise upgrade --monorepo` is not implemented yet.
Do not uninstall the versions that were upgraded away from

The old version is left in place and is not scheduled for removal. Use this when something outside mise points at the install directory.

Set `upgrade.auto_prune = false` to make this the default.

Immediately uninstall the versions that were upgraded away from

Use this to bypass `upgrade.prune_after`, or to override `upgrade.auto_prune = false` for a single run.

Connect backend install command stdin/stdout/stderr directly to the terminal Implies --jobs=1
Print help Arguments:
<INSTALLED_TOOL@VERSION>
Tool(s) to upgrade e.g.: node@20 python@3.10 If not specified, all current tools will be upgraded

Installs a tool and adds the version to mise.toml.

This will install the tool version if it is not already installed. By default, this will use a `mise.toml` file in the current directory. If multiple config files exist (e.g., both `mise.toml` and `mise.local.toml`), the lowest precedence file (`mise.toml`) will be used. See https://mise.jdx.dev/configuration.html#target-file-for-write-operations

In the following order:
- If `--global` is set, it will use the global config file.
- If `--path` is set, it will use the config file at the given path.
- If `--env` is set, it will use `mise.<env>.toml`.
- If [`MISE_DEFAULT_CONFIG_FILENAME`](https://mise.jdx.dev/configuration.html#mise_default_config_filename) is set, it will use that instead.
- If `MISE_OVERRIDE_CONFIG_FILENAMES` is set, it will the first from that list.
- Otherwise just "mise.toml" or global config if cwd is home directory.

Use [`MISE_GLOBAL_CONFIG_FILE`](https://mise.jdx.dev/configuration.html#mise_global_config_file) to choose a different global config path.

Use the `--global` flag to use the global config file instead.

Usage: mise use [OPTIONS] [TOOL@VERSION]…

Options:

Create/modify an environment-specific config file like .mise.<env>.toml
Force reinstall even if already installed
Use the global config file (`~/.config/mise/config.toml`) instead of the local one
Number of jobs to run in parallel Values below 1 are treated as 1 [default: 4]
Environment: MISE_JOBS
Perform a dry run, showing what would be installed and modified without making changes
Specify a path to a config file or directory

If a directory is specified, it will look for a config file in that directory following the rules above.

Like --dry-run but exits with code 1 if there are changes to make

This is useful for scripts to check if tools need to be added or removed.

Save fuzzy version to config file

e.g.: `mise use --fuzzy node@20` will save 20 as the version this is the default behavior unless `MISE_PIN=1`

Only install versions released before this date or older than this duration

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y".

Save the resolved concrete version to the config file

If the request exactly matches an available release, that release is preferred over installed fuzzy matches. Use `prefix:` to explicitly request recursive prefix matching. e.g.: `mise use --pin node@20` will save the resolved `20.x.y` version Set `MISE_PIN=1` to make this the default behavior

Consider using mise.lock as a better alternative to pinning in mise.toml: https://mise.jdx.dev/configuration/settings.html#lockfile

Connect backend install command stdin/stdout/stderr directly to the terminal Implies `--jobs=1`
Remove the tool(s) from config file
Print help
Command to run after installing this tool Arguments:
<TOOL@VERSION>
Tool to add to config file

e.g.: node@20, cargo:ripgrep@latest npm:prettier@3 If no version is specified, it will default to @latest

Tool options can be set with this syntax:


mise use ubi:BurntSushi/ripgrep[exe=rg]

Display the version of mise

Displays the version, os, architecture, and the date of the build.

If the version is out of date, it will display a warning.

Usage: mise version [OPTIONS]

Options:

Print the version information in JSON format
Print help

Run task(s) and watch for changes to rerun it

This command uses the `watchexec` tool to watch for changes to files and rerun the specified task(s). It must be installed for this command to work, but you can install it with `mise use -g watchexec@latest`.

For more advanced process management (daemon management, auto-restart, readiness checks, cron scheduling), see mise's sister project: https://pitchfork.jdx.dev

Usage: mise watch [OPTIONS] [<TASK>] [<ARGS>] ...

Options:

Tasks to run
Files to watch Defaults to sources from the task(s)
Run only the specified tasks skipping all dependencies
Watch a specific file or directory

By default, Watchexec watches the current directory.

When watching a single file, it's often better to watch the containing directory instead, and filter on the filename. Some editors may replace the file with a new one when saving, and some platforms may not detect that or further changes.

Upon starting, Watchexec resolves a "project origin" from the watched paths. See the help for '--project-origin' for more information.

This option can be specified multiple times to watch multiple files or directories.

The special value '/dev/null', provided as the only path watched, will cause Watchexec to not watch any paths. Other event sources (like signals or key events) may still be used.

Watch a specific directory, non-recursively

Unlike '-w', folders watched with this option are not recursed into.

This option can be specified multiple times to watch multiple directories non-recursively.

Watch files and directories from a file

Each line in the file will be interpreted as if given to '-w'.

For more complex uses (like watching non-recursively), use the argfile capability: build a file containing command-line options and pass it to watchexec with `@path/to/argfile`.

The special value '-' will read from STDIN; this in incompatible with '--stdin-quit'.

Clear screen before running command

If this doesn't completely clear the screen, try '--clear=reset'.

What to do when receiving events while the command is running

Default is to 'do-nothing', which ignores events while the command is running, so that changes that occur due to the command are ignored, like compilation outputs. You can also use 'queue' which will run the command once again when the current run has finished if any events occur while it's running, or 'restart', which terminates the running command and starts a new one. Finally, there's 'signal', which only sends a signal; this can be useful with programs that can reload their configuration without a full restart.

The signal can be specified with the '--signal' option.

Default: do-nothing
Restart the process if it's still running

This is a shorthand for '--on-busy-update=restart'.

Send a signal to the process when it's still running

Specify a signal to send to the process when it's still running. This implies '--on-busy-update=signal'; otherwise the signal used when that mode is 'restart' is controlled by '--stop-signal'.

See the long documentation for '--stop-signal' for syntax.

Signals are not supported on Windows at the moment, and will always be overridden to 'kill'. See '--stop-signal' for more on Windows "signals".

Signal to send to stop the command

This is used by 'restart' and 'signal' modes of '--on-busy-update' (unless '--signal' is provided). The restart behaviour is to send the signal, wait for the command to exit, and if it hasn't exited after some time (see '--timeout-stop'), forcefully terminate it.

The default on unix is "SIGTERM".

Input is parsed as a full signal name (like "SIGTERM"), a short signal name (like "TERM"), or a signal number (like "15"). All input is case-insensitive.

On Windows this option is technically supported but only supports the "KILL" event, as Watchexec cannot yet deliver other events. Windows doesn't have signals as such; instead it has termination (here called "KILL" or "STOP") and "CTRL+C", "CTRL+BREAK", and "CTRL+CLOSE" events. For portability the unix signals "SIGKILL", "SIGINT", "SIGTERM", and "SIGHUP" are respectively mapped to these.

Time to wait for the command to exit gracefully

This is used by the 'restart' mode of '--on-busy-update'. After the graceful stop signal is sent, Watchexec will wait for the command to exit. If it hasn't exited after this time, it is forcefully terminated.

Takes a unit-less value in seconds, or a time span value such as "5min 20s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.

The default is 10 seconds. Set to 0 to immediately force-kill the command.

This has no practical effect on Windows as the command is always forcefully terminated; see '--stop-signal' for why.

Default: 10s
Translate signals from the OS to signals to send to the command

Takes a pair of signal names, separated by a colon, such as "TERM:INT" to map SIGTERM to SIGINT. The first signal is the one received by watchexec, and the second is the one sent to the command. The second can be omitted to discard the first signal, such as "TERM:" to not do anything on SIGTERM.

If SIGINT or SIGTERM are mapped, then they no longer quit Watchexec. Besides making it hard to quit Watchexec itself, this is useful to send pass a Ctrl-C to the command without also terminating Watchexec and the underlying program with it, e.g. with "INT:INT".

This option can be specified multiple times to map multiple signals.

Signal syntax is case-insensitive for short names (like "TERM", "USR2") and long names (like "SIGKILL", "SIGHUP"). Signal numbers are also supported (like "15", "31"). On Windows, the forms "STOP", "CTRL+C", and "CTRL+BREAK" are also supported to receive, but Watchexec cannot yet deliver other "signals" than a STOP.

Time to wait for new events before taking action

When an event is received, Watchexec will wait for up to this amount of time before handling it (such as running the command). This is essential as what you might perceive as a single change may actually emit many events, and without this behaviour, Watchexec would run much too often. Additionally, it's not infrequent that file writes are not atomic, and each write may emit an event, so this is a good way to avoid running a command while a file is partially written.

An alternative use is to set a high value (like "30min" or longer), to save power or bandwidth on intensive tasks, like an ad-hoc backup script. In those use cases, note that every accumulated event will build up in memory.

Takes a unit-less value in milliseconds, or a time span value such as "5sec 20ms". Providing a unit-less value is deprecated and will warn; it will be an error in the future.

The default is 50 milliseconds. Setting to 0 is highly discouraged.

Default: 50ms
Exit when stdin closes

This watches the stdin file descriptor for EOF, and exits Watchexec gracefully when it is closed. This is used by some process managers to avoid leaving zombie processes around.

Don't load gitignores

Among other VCS exclude files, like for Mercurial, Subversion, Bazaar, DARCS, Fossil. Note that Watchexec will detect which of these is in use, if any, and only load the relevant files. Both global (like '~/.gitignore') and local (like '.gitignore') files are considered.

This option is useful if you want to watch files that are ignored by Git.

Don't load project-local ignores

This disables loading of project-local ignore files, like '.gitignore' or '.ignore' in the watched project. This is contrasted with '--no-vcs-ignore', which disables loading of Git and other VCS ignore files, and with '--no-global-ignore', which disables loading of global or user ignore files, like '~/.gitignore' or '~/.config/watchexec/ignore'.

Supported project ignore files:


- Git: .gitignore at project root and child directories, .git/info/exclude, and the file pointed to by `core.excludesFile` in .git/config.
- Mercurial: .hgignore at project root and child directories.
- Bazaar: .bzrignore at project root.
- Darcs: _darcs/prefs/boring
- Fossil: .fossil-settings/ignore-glob
- Ripgrep/Watchexec/generic: .ignore at project root and child directories.

VCS ignore files (Git, Mercurial, Bazaar, Darcs, Fossil) are only used if the corresponding VCS is discovered to be in use for the project/origin. For example, a .bzrignore in a Git repository will be discarded.

Don't load global ignores

This disables loading of global or user ignore files, like '~/.gitignore', '~/.config/watchexec/ignore', or '%APPDATA%\Bazaar\2.0\ignore'. Contrast with '--no-vcs-ignore' and '--no-project-ignore'.

Supported global ignore files


- Git (if core.excludesFile is set): the file at that path
- Git (otherwise): the first found of $XDG_CONFIG_HOME/git/ignore, %APPDATA%/.gitignore, %USERPROFILE%/.gitignore, $HOME/.config/git/ignore, $HOME/.gitignore.
- Bazaar: the first found of %APPDATA%/Bazaar/2.0/ignore, $HOME/.bazaar/ignore.
- Watchexec: the first found of $XDG_CONFIG_HOME/watchexec/ignore, %APPDATA%/watchexec/ignore, %USERPROFILE%/.watchexec/ignore, $HOME/.watchexec/ignore.

Like for project files, Git and Bazaar global files will only be used for the corresponding VCS as used in the project.

Don't use internal default ignores

Watchexec has a set of default ignore patterns, such as editor swap files, `*.pyc`, `*.pyo`, `.DS_Store`, `.bzr`, `_darcs`, `.fossil-settings`, `.git`, `.hg`, `.pijul`, `.svn`, and Watchexec log files.

Don't discover ignore files at all

This is a shorthand for '--no-global-ignore', '--no-vcs-ignore', '--no-project-ignore', but even more efficient as it will skip all the ignore discovery mechanisms from the get go.

Note that default ignores are still loaded, see '--no-default-ignore'.

Don't ignore anything at all

This is a shorthand for '--no-discover-ignore', '--no-default-ignore'.

Note that ignores explicitly loaded via other command line options, such as '--ignore' or '--ignore-file', will still be used.

Wait until first change before running command

By default, Watchexec will run the command once immediately. With this option, it will instead wait until an event is detected before running the command as normal.

Sleep before running the command

This option will cause Watchexec to sleep for the specified amount of time before running the command, after an event is detected. This is like using "sleep 5 && command" in a shell, but portable and slightly more efficient.

Takes a unit-less value in seconds, or a time span value such as "2min 5s". Providing a unit-less value is deprecated and will warn; it will be an error in the future.

Poll for filesystem changes

By default, and where available, Watchexec uses the operating system's native file system watching capabilities. This option disables that and instead uses a polling mechanism, which is less efficient but can work around issues with some file systems (like network shares) or edge cases.

Optionally takes a unit-less value in milliseconds, or a time span value such as "2s 500ms", to use as the polling interval. If not specified, the default is 30 seconds. Providing a unit-less value is deprecated and will warn; it will be an error in the future.

Aliased as '--force-poll'.

Use a different shell

By default, Watchexec will use '$SHELL' if it's defined or a default of 'sh' on Unix-likes, and either 'pwsh', 'powershell', or 'cmd' (CMD.EXE) on Windows, depending on what Watchexec detects is the running shell.

With this option, you can override that and use a different shell, for example one with more features or one which has your custom aliases and functions.

If the value has spaces, it is parsed as a command line, and the first word used as the shell program, with the rest as arguments to the shell.

The command is run with the '-c' flag (except for 'cmd' on Windows, where it's '/C').

The special value 'none' can be used to disable shell use entirely. In that case, the command provided to Watchexec will be parsed, with the first word being the executable and the rest being the arguments, and executed directly. Note that this parsing is rudimentary, and may not work as expected in all cases.

Using 'none' is a little more efficient and can enable a stricter interpretation of the input, but it also means that you can't use shell features like globbing, redirection, control flow, logic, or pipes.

Examples:

Use without shell:


$ watchexec -n -- zsh -x -o shwordsplit scr

Use with powershell core:


$ watchexec --shell=pwsh -- Test-Connection localhost

Use with CMD.exe:


$ watchexec --shell=cmd -- dir

Use with a different unix shell:


$ watchexec --shell=bash -- 'echo $BASH_VERSION'

Use with a unix shell and options:


$ watchexec --shell='zsh -x -o shwordsplit' -- scr

Shorthand for '--shell=none'
Configure event emission

Watchexec can emit event information when running a command, which can be used by the child process to target specific changed files.

One thing to take care with is assuming inherent behaviour where there is only chance. Notably, it could appear as if the `RENAMED` variable contains both the original and the new path being renamed. In previous versions, it would even appear on some platforms as if the original always came before the new. However, none of this was true. It's impossible to reliably and portably know which changed path is the old or new, "half" renames may appear (only the original, only the new), "unknown" renames may appear (change was a rename, but whether it was the old or new isn't known), rename events might split across two debouncing boundaries, and so on.

This option controls where that information is emitted. It defaults to 'none', which doesn't emit event information at all. The other options are 'environment' (deprecated), 'stdio', 'file', 'json-stdio', and 'json-file'.

The 'stdio' and 'file' modes are text-based: 'stdio' writes absolute paths to the stdin of the command, one per line, each prefixed with `create:`, `remove:`, `rename:`, `modify:`, or `other:`, then closes the handle; 'file' writes the same thing to a temporary file, and its path is given with the $WATCHEXEC_EVENTS_FILE environment variable.

There are also two JSON modes, which are based on JSON objects and can represent the full set of events Watchexec handles. Here's an example of a folder being created on Linux:

```json
{
"tags": [
{
"kind": "path",
"absolute": "/home/user/your/new-folder",
"filetype": "dir"
},
{
"kind": "fs",
"simple": "create",
"full": "Create(Folder)"
},
{
"kind": "source",
"source": "filesystem",
}
],
"metadata": {
"notify-backend": "inotify"
}
} ```

The fields are as follows:


- `tags`, structured event data.
- `tags[].kind`, which can be:
* 'path', along with:
+ `absolute`, an absolute path.
+ `filetype`, a file type if known ('dir', 'file', 'symlink', 'other').
* 'fs':
+ `simple`, the "simple" event type ('access', 'create', 'modify', 'remove', or 'other').
+ `full`, the "full" event type, which is too complex to fully describe here, but looks like 'General(Precise(Specific))'.
* 'source', along with:
+ `source`, the source of the event ('filesystem', 'keyboard', 'mouse', 'os', 'time', 'internal').
* 'keyboard', along with:
+ `keycode`. Currently only the value 'eof' is supported.
* 'process', for events caused by processes:
+ `pid`, the process ID.
* 'signal', for signals sent to Watchexec:
+ `signal`, the normalised signal name ('hangup', 'interrupt', 'quit', 'terminate', 'user1', 'user2').
* 'completion', for when a command ends:
+ `disposition`, the exit disposition ('success', 'error', 'signal', 'stop', 'exception', 'continued').
+ `code`, the exit, signal, stop, or exception code.
- `metadata`, additional information about the event.

The 'json-stdio' mode will emit JSON events to the standard input of the command, one per line, then close stdin. The 'json-file' mode will create a temporary file, write the events to it, and provide the path to the file with the $WATCHEXEC_EVENTS_FILE environment variable.

Finally, the 'environment' mode was the default until 2.0. It sets environment variables with the paths of the affected files, for filesystem events:

$WATCHEXEC_COMMON_PATH is set to the longest common path of all of the below variables, and so should be prepended to each path to obtain the full/real path. Then:


- $WATCHEXEC_CREATED_PATH is set when files/folders were created
- $WATCHEXEC_REMOVED_PATH is set when files/folders were removed
- $WATCHEXEC_RENAMED_PATH is set when files/folders were renamed
- $WATCHEXEC_WRITTEN_PATH is set when files/folders were modified
- $WATCHEXEC_META_CHANGED_PATH is set when files/folders' metadata were modified
- $WATCHEXEC_OTHERWISE_CHANGED_PATH is set for every other kind of pathed event

Multiple paths are separated by the system path separator, ';' on Windows and ':' on unix. Within each variable, paths are deduplicated and sorted in binary order (i.e. neither Unicode nor locale aware).

This is the legacy mode, is deprecated, and will be removed in the future. The environment is a very restricted space, while also limited in what it can usefully represent. Large numbers of files will either cause the environment to be truncated, or may error or crash the process entirely. The $WATCHEXEC_COMMON_PATH is also unintuitive, as demonstrated by the multiple confused queries that have landed in my inbox over the years.

Default: none
Only emit events to stdout, run no commands.

This is a convenience option for using Watchexec as a file watcher, without running any commands. It is almost equivalent to using `cat` as the command, except that it will not spawn a new process for each event.

This option requires `--emit-events-to` to be set, and restricts the available modes to `stdio` and `json-stdio`, modifying their behaviour to write to stdout instead of the stdin of the command.

Add env vars to the command

This is a convenience option for setting environment variables for the command, without setting them for the Watchexec process itself.

Use key=value syntax. Multiple variables can be set by repeating the option.

Configure how the process is wrapped

By default, Watchexec will run the command in a session on macOS, in a process group on other Unix platforms, and in a Job Object in Windows.

Some Unix programs prefer running in a session, while others do not work in a process group.

Use 'group' to use a process group, 'session' to use a process session, and 'none' to run the command directly. On Windows, either of 'group' or 'session' will use a Job Object.

Alert when commands start and end

With this, Watchexec will emit a desktop notification when a command starts and ends, on supported platforms. On unsupported platforms, it may silently do nothing, or log a warning.

When to use terminal colours

Setting the environment variable `NO_COLOR` to any value is equivalent to `--color=never`.

Default: auto
Print how long the command took to run

This may not be exactly accurate, as it includes some overhead from Watchexec itself. Use the `time` utility, high-precision timers, or benchmarking tools for more accurate results.

Don't print starting and stopping messages

By default Watchexec will print a message when the command starts and stops. This option disables this behaviour, so only the command's output, warnings, and errors will be printed.

Ring the terminal bell on command completion
Set the project origin

Watchexec will attempt to discover the project's "origin" (or "root") by searching for a variety of markers, like files or directory patterns. It does its best but sometimes gets it it wrong, and you can override that with this option.

The project origin is used to determine the path of certain ignore files, which VCS is being used, the meaning of a leading '/' in filtering patterns, and maybe more in the future.

When set, Watchexec will also not bother searching, which can be significantly faster.

Set the working directory

By default, the working directory of the command is the working directory of Watchexec. You can change that with this option. Note that paths may be less intuitive to use with this.

Filename extensions to filter to

This is a quick filter to only emit events for files with the given extensions. Extensions can be given with or without the leading dot (e.g. 'js' or '.js'). Multiple extensions can be given by repeating the option or by separating them with commas.

Filename patterns to filter to

Provide a glob-like filter pattern, and only events for files matching the pattern will be emitted. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.

Files to load filters from

Provide a path to a file containing filters, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--filter' option.

This can also be used via the $WATCHEXEC_FILTER_FILES environment variable.

Environment: WATCHEXEC_FILTER_FILES
[experimental] Filter programs.

/!\ This option is EXPERIMENTAL and may change and/or vanish without notice.

Provide your own custom filter programs in jaq (similar to jq) syntax. Programs are given an event in the same format as described in '--emit-events-to' and must return a boolean. Invalid programs will make watchexec fail to start; use '-v' to see program runtime errors.

In addition to the jaq stdlib, watchexec adds some custom filter definitions:


- 'path | file_meta' returns file metadata or null if the file does not exist.


- 'path | file_size' returns the size of the file at path, or null if it does not exist.


- 'path | file_read(bytes)' returns a string with the first n bytes of the file at path.
If the file is smaller than n bytes, the whole file is returned. There is no filter to
read the whole file at once to encourage limiting the amount of data read and processed.


- 'string | hash', and 'path | file_hash' return the hash of the string or file at path.
No guarantee is made about the algorithm used: treat it as an opaque value.


- 'any | kv_store(key)', 'kv_fetch(key)', and 'kv_clear' provide a simple key-value store.
Data is kept in memory only, there is no persistence. Consistency is not guaranteed.


- 'any | printout', 'any | printerr', and 'any | log(level)' will print or log any given
value to stdout, stderr, or the log (levels = error, warn, info, debug, trace), and
pass the value through (so '[1] | log("debug") | .[]' will produce a '1' and log '[1]').

All filtering done with such programs, and especially those using kv or filesystem access, is much slower than the other filtering methods. If filtering is too slow, events will back up and stall watchexec. Take care when designing your filters.

If the argument to this option starts with an '@', the rest of the argument is taken to be the path to a file containing a jaq program.

Jaq programs are run in order, after all other filters, and short-circuit: if a filter (jaq or not) rejects an event, execution stops there, and no other filters are run. Additionally, they stop after outputting the first value, so you'll want to use 'any' or 'all' when iterating, otherwise only the first item will be processed, which can be quite confusing!

Find user-contributed programs or submit your own useful ones at https://github.com/watchexec/watchexec/discussions/592.

## Examples:

Regexp ignore filter on paths:


'all(.tags[] | select(.kind == "path"); .absolute | test("[.]test[.]js$")) | not'

Pass any event that creates a file:


'any(.tags[] | select(.kind == "fs"); .simple == "create")'

Pass events that touch executable files:


'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | metadata | .executable)'

Ignore files that start with shebangs:


'any(.tags[] | select(.kind == "path" && .filetype == "file"); .absolute | read(2) == "#!") | not'

Filename patterns to filter out

Provide a glob-like filter pattern, and events for files matching the pattern will be excluded. Multiple patterns can be given by repeating the option. Events that are not from files (e.g. signals, keyboard events) will pass through untouched.

Files to load ignores from

Provide a path to a file containing ignores, one per line. Empty lines and lines starting with '#' are ignored. Uses the same pattern format as the '--ignore' option.

This can also be used via the $WATCHEXEC_IGNORE_FILES environment variable.

Environment: WATCHEXEC_IGNORE_FILES
Filesystem events to filter to

This is a quick filter to only emit events for the given types of filesystem changes. Choose from 'access', 'create', 'remove', 'rename', 'modify', 'metadata'. Multiple types can be given by repeating the option or by separating them with commas. By default, this is all types except for 'access'.

This may apply filtering at the kernel level when possible, which can be more efficient, but may be more confusing when reading the logs.

Default: create,remove,rename,modify,metadata
Don't emit fs events for metadata changes

This is a shorthand for '--fs-events create,remove,rename,modify'. Using it alongside the '--fs-events' option is non-sensical and not allowed.

Print events that trigger actions

This prints the events that triggered the action when handling it (after debouncing), in a human readable form. This is useful for debugging filters.

Use '-vvv' instead when you need more diagnostic information.

Show the manual page

This shows the manual page for Watchexec, if the output is a terminal and the 'man' program is available. If not, the manual page is printed to stdout in ROFF format (suitable for writing to a watchexec.1 file).

Print help Arguments:
<TASK>
Tasks to run Can specify multiple tasks by separating with `:::` e.g.: `mise run task1 arg1 arg2 ::: task2 arg1 arg2` Defaults to `default`
<ARGS>
Task and arguments to run

Display the installation path for a tool

The tool must be installed for this to work.

Usage: mise where [OPTIONS] <TOOL@VERSION> [<ASDF_VERSION>]

Options:

Print help Arguments:
<TOOL@VERSION>
Tool(s) to look up e.g.: ruby@3 if "@<PREFIX>" is specified, it will show the latest installed version that matches the prefix otherwise, it will show the current, active installed version
<ASDF_VERSION>
the version prefix to use when querying the latest version same as the first argument after the "@" used for asdf compatibility

Shows the path that a tool's bin points to.

Use this to figure out what version of a tool is currently active.

Usage: mise which [OPTIONS] [<BIN_NAME>]

Options:

Use a specific tool@version e.g.: `mise which npm --tool=node@20`
Show the plugin name instead of the path
Show the version instead of the path
Print help Arguments:
<BIN_NAME>
The bin to look up

Jeff Dickey <@jdx>