MISE(1) General Commands Manual MISE(1) NAME mise - Dev tools, env vars, and tasks in one CLI SYNOPSIS mise [OPTIONS] [] [] ... [] ... [COMMAND] DESCRIPTION mise installs the development tools your projects need, sets their environment variables, and runs their tasks. You declare tools, environment variables, and tasks in mise.toml. `mise use ` installs a tool and adds it to the project's mise.toml, `mise install` installs everything the config requests, and `mise run ` runs a task. Docs: https://mise.jdx.dev OPTIONS -c, --continue-on-error Continue running tasks even if one fails -C, --cd Run as if mise were started in DIR -E, --env Load the `mise..toml` config files (same as MISE_ENV) Repeat the flag or separate names with commas to load several environments. -f, --force Force the operation -j, --jobs How many jobs to run in parallel; defaults to the `jobs` setting Values below 1 are treated as 1. Environment: MISE_JOBS -n, --dry-run Dry run, don't actually do anything -P, --profile Set the profile (environment) -q, --quiet Suppress non-error messages Environment: MISE_QUIET -s, --shell -t, --tool Tools to load in addition to those in mise.toml, such as `node@24 python@3.13` -v, --verbose Show extra output (use -vv for even more) -V, --version -y, --yes Answer yes to all confirmation prompts --debug Set the log level to debug --log-level --no-config Do not load any config files Same as `MISE_NO_CONFIG=1`. --no-env Do not load environment variables from config files Same as `MISE_NO_ENV=1`. --no-hooks Do not run hooks from config files Same as `MISE_NO_HOOKS=1`. --no-timings Hide the elapsed time printed after each task completes Set `MISE_TASK_TIMINGS=0` to hide it by default --output How task output is displayed when running a task (same as `mise run --output`) --raw Connect tasks and install commands directly to the terminal Commands then run one at a time. Same as `MISE_RAW=1` or the `raw` setting. --locked Require download URLs from the lockfile when installing Installing fails when the lockfile has no pre-resolved URL for a tool on the current platform, so mise does not call the GitHub or aqua registry APIs to find one. Same as `MISE_LOCKED=1` or the `locked` setting. --silent Suppress all task output and mise non-error messages --timings Show the elapsed time after each task completes Set `MISE_TASK_TIMINGS=1` to show it by default --trace Set the log level to trace -h, --help Print help ARGUMENTS Task to run Shorthand for `mise run `. Task arguments COMMANDS activate Print the script to activate mise in an interactive shell tool-alias Manage tool backend and version aliases Aliases: alias, aliases tool-alias get Show the version a tool's version alias stands for tool-alias ls List tool version aliases Aliases: list tool-alias set Set a backend alias or a version alias in the global config Aliases: add, create tool-alias unset Remove a backend alias or a version alias from the global config Aliases: rm, remove, delete, del backends Manage backends Aliases: b, backend, backend-list backends ls List built-in backends Aliases: list backends switch Switch tools to the backend the registry now installs them from bin-paths List the bin directories of the active tools bootstrap Set up this machine from your mise config Aliases: bs bootstrap accounts Manage Linux users and groups bootstrap accounts apply Create, update, or remove the configured Linux users and groups bootstrap accounts status Show the state of the configured Linux users and groups bootstrap compose Manage Docker Compose projects from `[bootstrap.compose]` bootstrap compose apply Apply Docker Compose projects from `[bootstrap.compose]` bootstrap compose status Show the state of Docker Compose projects from `[bootstrap.compose]` bootstrap files Manage system files and directories declared in `[bootstrap]` bootstrap files apply Create, update, or remove the configured system files and directories bootstrap files status Show the state of the configured system files and directories bootstrap firewall Manage the Linux host firewall from `[bootstrap.linux.firewall]` bootstrap firewall apply Apply the firewall from `[bootstrap.linux.firewall]` bootstrap firewall status Show the state of the firewall from `[bootstrap.linux.firewall]` bootstrap linux Manage systemd user units from `[bootstrap.linux.systemd.units]` bootstrap linux systemd-units Manage systemd user units from `[bootstrap.linux.systemd.units]` Aliases: systemd bootstrap linux systemd-units apply Install and start the configured systemd user units bootstrap linux systemd-units status Show the state of the configured systemd user units bootstrap macos Manage macOS preferences and LaunchAgents from `[bootstrap.settings.macos]` and `[bootstrap.macos.launchd]` bootstrap macos defaults Manage macOS preferences such as Dock, Finder, and keyboard settings bootstrap macos defaults apply Write the configured macOS preferences bootstrap macos defaults status Show the state of the configured macOS preferences bootstrap macos launchd-agents Manage macOS LaunchAgents from `[bootstrap.macos.launchd.agents]` Aliases: launchd bootstrap macos launchd-agents apply Install and load LaunchAgents from `[bootstrap.macos.launchd.agents]` bootstrap macos launchd-agents status Show the state of the configured LaunchAgents bootstrap mise-shell-activate Manage mise shell activation from `[bootstrap.mise_shell_activate]` Aliases: shell bootstrap mise-shell-activate apply Write mise activation into the configured shell startup files bootstrap mise-shell-activate status Show the state of the configured shell activation bootstrap packages Manage packages from `[bootstrap.packages]` bootstrap packages apply Install or remove packages to match `[bootstrap.packages]` Aliases: i, install bootstrap packages brew Manage Homebrew tap URLs in `[bootstrap.brew.taps]` bootstrap packages brew tap Add a Homebrew tap URL to the global `[bootstrap.brew.taps]` bootstrap packages brew untap Remove Homebrew tap URLs from `[bootstrap.brew.taps]` Aliases: remove, rm bootstrap packages export Print the configured `nix:` packages as a NixOS module bootstrap packages import Record installed Homebrew formulae in `[bootstrap.packages]` bootstrap packages prune Uninstall packages that no config declares bootstrap packages status Show the state of packages from `[bootstrap.packages]` Aliases: ls, list bootstrap packages upgrade Upgrade installed packages from `[bootstrap.packages]` Aliases: up bootstrap packages use Add packages to `[bootstrap.packages]` and install them Aliases: u bootstrap packages where Print the `opt` path of an installed Homebrew formula bootstrap plan Show what applying bootstrap resources would change bootstrap plugins Manage package manager plugins declared in `[bootstrap.plugins]` bootstrap plugins apply Install package manager plugins declared in `[bootstrap.plugins]` bootstrap plugins status Show whether declared package manager plugins are installed bootstrap remote Bootstrap one or more machines over SSH bootstrap repos Manage Git repositories from `[bootstrap.repos]` bootstrap repos apply Clone missing Git repositories and check out configured refs bootstrap repos exec Run a command in each configured Git repository bootstrap repos status Show the state of Git repositories from `[bootstrap.repos]` bootstrap repos update Clone missing Git repositories and fast-forward the rest bootstrap secrets Inspect bootstrap secret inputs without revealing their values bootstrap secrets status Show whether declared bootstrap secret inputs are available bootstrap services Manage services from `[bootstrap.services]` bootstrap services apply Apply the service state declared in `[bootstrap.services]` bootstrap services remove Uninstall a user-scope service bootstrap services status Show the state of services from `[bootstrap.services]` bootstrap settings [experimental] Apply `[bootstrap.settings]` through bootstrap settings plugins bootstrap settings apply Write the settings that differ from `[bootstrap.settings]` bootstrap settings status Show each setting in `[bootstrap.settings]` and its current value bootstrap status Show the state of every configured bootstrap part Aliases: ls bootstrap unapply Remove what a config environment's bootstrap sections created bootstrap user Manage your login shell from `[bootstrap.user]` bootstrap user apply Set your login shell from `[bootstrap.user]` bootstrap user status Show whether your login shell matches `[bootstrap.user]` cache Manage the mise cache cache clear Delete cached data Aliases: c, clean cache path Print the cache directory path Aliases: dir cache prune Remove cache files that have not been accessed recently Aliases: p cache task [experimental] Inspect artifact cache entries for a task completion Generate shell completions Aliases: complete, completions config Manage config files Aliases: cfg, toml config explain Describe each key in a mise TOML file config get Print a value from one mise TOML file config ls List config files currently in use, from lowest to highest precedence Aliases: list config set Set a value in one mise TOML file deactivate Print the script to disable mise in the current shell session daemons [experimental] Manage project daemons with pitchfork Aliases: daemon daemons providers [experimental] Manage shared servers from global `[daemon_providers]` daemons providers ls [experimental] List shared servers daemons providers start [experimental] Start shared servers daemons providers stop [experimental] Stop shared servers (data is kept) daemons providers restart [experimental] Restart shared servers with their current configuration daemons start [experimental] Start project daemons and the daemons they depend on daemons register [experimental] Register project daemons for on-demand startup daemons stop [experimental] Stop project daemons daemons restart [experimental] Restart project daemons daemons ls [experimental] List project daemons Aliases: list daemons urls [experimental] Show each daemon's URL and port daemons logs [experimental] Show the output of project daemons daemons status [experimental] Show the status of project daemons daemons tui [experimental] Open the pitchfork dashboard daemons prune [experimental] Remove daemon state left by deleted projects dotfiles Deploy, track, and sync dotfiles Aliases: dot dotfiles add Start deploying a file, or copy its edits back to the source dotfiles apply Link, copy, and render `[dotfiles]` entries into place dotfiles capture Run a command and save tracked files before and after it dotfiles conflicts Compare both sides of a sync conflict dotfiles diff Show what `mise dot apply` would change dotfiles edit Open a dotfile's source in your editor dotfiles exclude Never save paths matching a glob dotfiles files List a directory's files and whether each one is tracked dotfiles history Browse saved versions of your tracked files dotfiles history describe Set the description of a checkpoint dotfiles history diff Compare checkpoints, or your files against one dotfiles history ls List checkpoints, newest first Aliases: list dotfiles history purge Erase a path's saved versions from history dotfiles history show Show a checkpoint: its trigger, changes, and operation journal dotfiles include Stop excluding paths matching a glob dotfiles notify Send a test desktop notification dotfiles origin Show, connect, or disconnect the origin repository dotfiles origin set Connect an origin repository dotfiles paths List tracked paths and how they are saved dotfiles pull Write fetched changes from other machines to tracked files dotfiles recover Recover an interrupted dotfile operation dotfiles rollback Return files to the version a checkpoint holds dotfiles save Save a checkpoint of the tracked files now dotfiles status Show the state of your dotfiles and their history Aliases: ls dotfiles sync Push saved checkpoints and fetch incoming changes dotfiles track Track a file or directory in place dotfiles unapply Remove files that `mise dot apply` deployed dotfiles undo Reverse the tracked-file changes from an operation dotfiles untrack Stop tracking a file or directory dotfiles watch Save tracked files as they change doctor Check your mise setup for problems Aliases: dr doctor path Print the directories mise adds to PATH Aliases: paths doctor project Run the project's diagnostic checks en Start a subshell with mise's tools and environment env Print the environment for the current configuration Aliases: e exec Run a command with mise's tools and environment Aliases: x fmt Format mise TOML configuration generate Generate project files such as CI workflows, git hooks, and scripts Aliases: gen, g generate config Generate a mise.toml file generate devcontainer Generate a devcontainer configuration that installs mise and the project's tools generate git-pre-commit Generate a git hook that runs a mise task Aliases: pre-commit generate github-action Generate a GitHub Actions workflow that runs a mise task generate install-script Generate a script that downloads and runs a pinned mise generate task-docs Generate Markdown documentation for project tasks generate task-stubs Generate scripts that run mise tasks generate tool-stub Generate or update a tool stub implode Remove the mise CLI and all related data edit Edit mise.toml interactively install Install the tools in your config, or specific tool versions Aliases: i install-into Install a tool version into a directory outside mise installs [experimental] Inspect and choose identity-layout installations installs ls List the installations of the identity install layout Aliases: list installs migrate Reinstall legacy installations into the identity install layout installs select Choose which installation mise uses when no lockfile pins one latest Print the latest version that matches a version request link Symlink a tool version into mise Aliases: ln lock Create or refresh lockfile versions, checksums, and download URLs ls List installed and active tool versions Aliases: list ls-remote List tool versions available to install Aliases: list-all, list-remote lsp Run the language server for mise config files over stdin/stdout mcp Run the Model Context Protocol server over stdin/stdout oci [experimental] Build, push, and run OCI images of a project's tools oci build [experimental] Build an OCI image from the current mise.toml oci push [experimental] Build an OCI image and push it to a registry oci run [experimental] Build the project's image and run a command in it packslip Inspect and reset the signers mise has pinned for packslip tools packslip forget Forget a project's pinned signer so the next accepted release sets it packslip pins List the signer mise has pinned for each packslip project Aliases: list outdated Show outdated tool versions patrons Show the individuals supporting mise as Patron-tier members plugins Manage plugins Aliases: p, plugin, plugin-list plugins install Install plugins from a configured source, Git URL, or archive Aliases: i, a, add plugins link Link a local plugin directory into mise for development Aliases: ln plugins ls List installed plugins Aliases: list plugins ls-remote List registry tools that have an asdf or vfox plugin backend Aliases: list-remote, list-all plugins uninstall Remove an installed plugin Aliases: remove, rm plugins update Update installed plugins Aliases: up, upgrade deps [experimental] Manage project dependencies Aliases: dep, prepare deps add Add packages to the project's dependencies deps install Install project dependencies deps remove Remove packages from the project's dependencies prune Delete tool versions that nothing uses registry List registry shorthand names and their backends reshim Create shims for executables provided by installed tools run Run tasks and their dependencies Aliases: r search Search for available tools secrets [experimental] Inspect the project's secrets source secrets ls [experimental] List secret names from the project's secrets source Aliases: list self-update Update mise itself set Set, show, or list environment variables in mise.toml Aliases: ev, env-vars settings Manage settings settings add Append a value to an array setting settings get Show the effective value of a setting settings ls List configured settings and their sources Aliases: list settings set Set a setting Aliases: create settings unset Remove a setting from the global or project config Aliases: rm, remove, delete, del shell Set a tool version for the current shell session Aliases: sh ssh Open an SSH session, optionally borrowing read-only GitHub access shell-alias Manage shell aliases shell-alias get Show the command for a shell alias shell-alias ls List shell aliases Aliases: list shell-alias set Set a shell alias in the global config Aliases: add, create shell-alias unset Remove a shell alias from the global config Aliases: rm, remove, delete, del skills List and link the agent skills that active tools ship Aliases: skill skills ls List the skills the active tools declare Aliases: list skills sync Link the active tools' skills where an agent looks for them sponsors Show the companies sponsoring mise and the jdx.dev open source tools sync Use tool versions installed by other version managers sync node Symlink node versions installed by nvm, nodenv, or Homebrew into mise sync python Symlink python versions installed by pyenv or uv into mise sync ruby Symlink ruby versions installed by Homebrew into mise tasks Manage tasks Aliases: t, task tasks add Add a task tasks deps Show the dependency tree of tasks tasks edit Open a task in your editor tasks graph Show the monorepo project graph tasks history Show recent task runs and how long they took tasks info Show a task's definition tasks log Print the output of a task's last run tasks ls List available tasks tasks rm Remove tasks Aliases: remove tasks set Change fields of an existing TOML task tasks validate Check task definitions for errors test-tool Test that a tool installs and runs token Show which Git provider token mise uses token forgejo Show the Forgejo token mise uses for a host token github Show the GitHub token mise uses for a host token gitlab Show the GitLab token mise uses for a host tool Show information about a tool tool-stub Run a tool stub file trust Mark a config file as trusted uninstall Remove installed tool versions unset Remove environment variables from mise.toml untrust Remove explicit trust for a config unuse Remove tool requests from config files and prune unused installations Aliases: rm, remove upgrade Upgrade outdated tools Aliases: up use Install a tool and add it to configuration Aliases: u vars List, set, and ask for config vars vars ls List every var, with the file it comes from Aliases: list vars prompt Ask for the prompt vars that have no saved answer, or set answers directly vars unset Forget saved answers so they are asked for again Aliases: rm, remove version Show the version of mise Aliases: v watch Run tasks and rerun them when files change Aliases: w where Show the install directory of a tool version which Show the path a tool's executable resolves to MISE ACTIVATE Print the script to activate mise in an interactive shell Evaluate this command's output with the syntax for your shell; running it alone only prints the script. Activation updates tools and environment variables as this shell changes directories. Add the matching example below once to your interactive startup file: ~/.bashrc for Bash, ~/.zshrc for Zsh, ~/.config/fish/config.fish for Fish, or $PROFILE for PowerShell. For Nushell, Elvish and other shells, see https://mise.jdx.dev/shell-setup.html. The mise executable must be on PATH before that line runs. Otherwise use its absolute path, for example `eval "$(~/.local/bin/mise activate zsh)"`. Use `mise exec -- command` for scripts and CI that do not need interactive hooks. The `status.*` settings control the messages mise prints when you change directories. Usage: mise activate [OPTIONS] [] Options: -q, --quiet Suppress non-error messages from the hook that runs at each prompt -s, --shell Shell type to generate the script for --no-hook-env Do not run hook-env automatically Use it for debugging: after `eval "$(mise activate zsh --no-hook-env)"`, run `mise hook-env` yourself to print the shell code it would evaluate, or `mise hook-env --trace` for more detail. --shims Put the shims directory on PATH instead of updating PATH at each prompt Roughly equivalent to: PATH="$HOME/.local/share/mise/shims:$PATH" Shims do not support every feature of `mise activate`; see https://mise.jdx.dev/dev-tools/shims.html#shims-vs-path. --status Show "mise: @" message when changing directories -h, --help Print help Arguments: Shell type to generate the script for Defaults to the shell named by MISE_SHELL or SHELL. mise reports an error when neither names a supported shell, as in PowerShell and cmd on Windows. Examples: Activate mise in Bash eval "$(mise activate bash)" Activate mise in Zsh eval "$(mise activate zsh)" Activate mise in Fish mise activate fish | source Activate mise in Xonsh execx($(mise activate xonsh)) Activate mise in PowerShell (&mise activate pwsh) | Out-String | Invoke-Expression MISE TOOL-ALIAS Manage tool backend and version aliases A backend alias makes a tool name install from another backend: `[tool_alias] ripgrep = "aqua:BurntSushi/ripgrep"`. A version alias names a version request: `[tool_alias.node.versions] project = "20"` lets you write `node@project`. With no subcommand, lists version aliases (same as `mise tool-alias ls`; the flags below are passed to it). See https://mise.jdx.dev/dev-tools/aliases.html Usage: mise tool-alias [OPTIONS] [COMMAND] Options: -p, --tool Filter aliases by tool --no-header Do not print the table header -h, --help Print help MISE TOOL-ALIAS GET Show the version a tool's version alias stands for Reads `[tool_alias.TOOL.versions]` from every loaded config file and the aliases the tool's backend provides, such as node's `lts-*` aliases. It prints the stored request, which may itself be a prefix. Usage: mise tool-alias get [OPTIONS] Options: -h, --help Print help Arguments: The tool to show the alias for The alias to show Examples: Show the version node's lts alias stands for mise tool-alias get node lts 26 Read back an alias you set mise tool-alias set node project 20 mise tool-alias get node project 20 MISE TOOL-ALIAS LS List tool version aliases Lists version aliases from `[tool_alias..versions]` in any loaded config file and the aliases that tool backends provide, such as node's `lts-*` names or an asdf plugin's `bin/list-aliases`. For example: [tool_alias.node.versions] project = "20" Backend aliases (`[tool_alias] tool = "backend"`) are not listed; run `mise tool ` to see the backend a tool uses. Usage: mise tool-alias ls [OPTIONS] [] Options: --no-header Do not print the table header -h, --help Print help Arguments: Only show aliases for this tool Examples: List node's version aliases mise tool-alias ls node tool alias version node lts 26 node lts-jod 22 node project 20 MISE TOOL-ALIAS SET Set a backend alias or a version alias in the global config `mise tool-alias set TOOL BACKEND` makes TOOL install from BACKEND, written as `[tool_alias] TOOL = "BACKEND"`. `mise tool-alias set TOOL ALIAS VERSION` makes `TOOL@ALIAS` mean VERSION, written under `[tool_alias.TOOL.versions]`. Writes the global config (~/.config/mise/config.toml by default); add aliases to a project's mise.toml to share them. Usage: mise tool-alias set [OPTIONS] [] Options: -h, --help Print help Arguments: The tool to alias The version alias to set, or the backend when VALUE is omitted The version request the alias stands for Examples: Install ripgrep from its aqua backend mise tool-alias set ripgrep aqua:BurntSushi/ripgrep Make node@project mean node@20 mise tool-alias set node project 20 MISE TOOL-ALIAS UNSET Remove a backend alias or a version alias from the global config With only TOOL, removes the tool's backend alias. With TOOL and ALIAS, removes that version alias. Edits the global config (~/.config/mise/config.toml by default). Usage: mise tool-alias unset [OPTIONS] [] Options: -h, --help Print help Arguments: The tool to remove the alias from The version alias to remove; omit it to remove the backend alias Examples: Remove ripgrep's backend alias mise tool-alias unset ripgrep Remove node's project version alias mise tool-alias unset node project MISE BACKENDS Manage backends A backend is where mise installs a tool from: a package registry such as npm or cargo, a release host such as GitHub, or a plugin. Each tool uses one, either written as a prefix (`npm:prettier`) or chosen by the registry. With no subcommand, lists the built-in backends. See https://mise.jdx.dev/dev-tools/backends/. Usage: mise backends [OPTIONS] [COMMAND] Options: -h, --help Print help MISE BACKENDS LS List built-in backends Backends that plugins add are listed by `mise plugins ls`. Usage: mise backends ls [OPTIONS] Options: -h, --help Print help Examples: List the backends built into mise mise backends ls MISE BACKENDS SWITCH Switch tools to the backend the registry now installs them from When the registry moves a tool to another backend, mise keeps installing it from the backend recorded in mise.lock and warns that the registry has a newer one. This moves those lock entries to the registry's backend at the same versions, relocks them to record the new backend's checksums and URLs, and reinstalls installed versions so they come from the new backend. It covers the lockfiles `mise lock` writes: the current project's, or the global config's with `--global`. Usage: mise backends switch [OPTIONS] [] ... Options: -n, --dry-run Show what would switch without changing the lockfile or installs -g, --global Switch tools in the global config's lockfile instead of the project's -h, --help Print help Arguments: Tools to switch Defaults to every configured tool whose locked backend the registry has replaced. A version (`hk@1.58.1`) limits the switch to that version. Examples: Move communique to the registry's current backend mise backends switch communique List every locked tool the registry now installs from another backend mise backends switch --dry-run MISE BIN-PATHS List the bin directories of the active tools Prints the bin directories of the tool versions the current config selects. It does not include `_.path` entries from [env]; `mise doctor path` lists everything mise adds to PATH. Usage: mise bin-paths [OPTIONS] [] ... Options: --bin-names Print executable names instead of bin directories -J, --json Print executables as JSON objects with `name`, `path`, and `symlink` (implies --bin-names) -h, --help Print help Arguments: Only list these tools, such as `ruby@3` Examples: Print the bin directory of every active tool mise bin-paths Print only node's bin directory mise bin-paths node List the executables the active tools provide mise bin-paths --bin-names MISE BOOTSTRAP Set up this machine from your mise config Applies each part your config declares, in this order. Each step names its parts as `--only` and `--skip` accept them, followed by any condition. 1. `accounts`, then `plugins` (package manager plugins) 2. `files` with `phase = "pre-packages"`, then built-in `packages` 3. The remaining `files`, then `services`, `firewall`, and `compose` 4. `repos`, then `dotfiles` 5. `mise-shell-activate`, `macos-defaults`, and `macos-launchd-agents` 6. `linux-systemd-units`, then `user` (the login shell) 7. `tools` 8. Plugin `packages`, then user `services` with `requires_tools = true` 9. `task` (the `bootstrap` task, if defined), then `final-hook` Hooks run before and after packages, repos, dotfiles, macOS defaults, the login shell, and tools. The post-packages hook runs right after built-in packages, or after plugin packages when any are configured. See https://mise.jdx.dev/bootstrap.html#how-it-runs. Parts that already match the config are left alone, but hooks and the `bootstrap` task run every time, so make them safe to repeat. Checking dotfile state can render templates, which may run `exec()`. Preview with `--dry-run`. To inspect without applying, use `mise bootstrap status` for current state or `mise bootstrap plan` for resource-level changes. Usage: mise bootstrap [OPTIONS] [COMMAND] Options: --from Clone a bootstrap project (a Git repository with a mise.toml) and apply it The checkout is reused on later runs; add `--update` to fast-forward it first. Append `?ref=` to check out a ref instead of the default branch, for example `https://github.com/example/workstation.git?ref=v1`. See https://mise.jdx.dev/bootstrap/from-repository.html. --adopt Clone a repository of global mise config or dotfile history, then apply it A repository of global config (`config.toml`, `conf.d/`, `tasks/`) is cloned into the global config directory, normally ~/.config/mise. A setup repository shared with `mise dotfiles origin set` restores its tracked files instead. `OWNER/REPO` is short for `https://github.com/OWNER/REPO.git`. Append `?ref=` to adopt a branch other than the default branch. --replace-history Discard this machine's dotfile history and adopt the repository's Use it with `--adopt` when the two histories are unrelated. Files that differ from the repository still stop the adoption until you resolve them, or add `--take-remote-all` to take the repository's version of each. --take-remote-all Take the setup repository's version of every existing file that differs while adopting The replaced versions are saved first, so `mise dot undo` restores them. --from-dir Directory for the `--from` checkout (default: `$MISE_DATA_DIR/bootstrap-repo`) --config-dir Link the global config directory to this directory of the `--from` checkout mise links its config directory, normally ~/.config/mise, to the directory, then bootstraps from it, so its `config.toml`, `config..toml`, `conf.d/`, and `miserc.toml` are the global config from this run on. The directory must exist in the checkout, and the path to it is relative to the checkout and must stay inside it; `.` is the checkout itself. mise's config directory, where the link goes, must be missing, empty, or already this link. See https://mise.jdx.dev/bootstrap/from-repository.html#global-config-elsewhere. -n, --dry-run Show what would change without changing anything Hooks and the `bootstrap` task are printed instead of run. -y, --yes Skip confirmation prompts --skip-dirty Skip configured repositories with local changes instead of failing --force-dotfiles Overwrite existing files that conflict with whole-file dotfile entries --prune-dotfiles Remove files that dotfile groups deployed but no active entry deploys now The same pruning as `mise dot apply --prune`, run at the end of the dotfiles phase before its post hook: files of a group that is no longer selected or declared, and files a group stopped deploying because of a new `exclude` or a deleted source. Changed copies stay in place, and mise asks before removing anything unless `--yes` is given or there is no terminal. With `--dry-run`, nothing is removed. --only Run only these parts Repeat the flag or separate parts with commas. Cannot be combined with `--skip`. --prompt-secrets Prompt securely for missing bootstrap secret inputs --prompt-vars Ask for `[vars]` entries that declare a `prompt` and have no saved answer mise saves each answer under `$MISE_STATE_DIR`, not in any config file, and never asks for it again. Without a terminal, a var keeps its default. A `--dry-run` still saves the answers it asks for. --save-env Save the environments of `-E` or `MISE_ENV` to `miserc.local.toml` Writes `env` in the `miserc.local.toml` of mise's config directory, so later runs, including `mise bootstrap --update`, select the same environments without `-E`. Names may be sets from `[env_sets]` in `miserc.toml`. Other keys in the file are kept. Needs `-E` or `MISE_ENV`, and a `--dry-run` writes nothing. --skip Skip these parts Repeat the flag or separate parts with commas. Cannot be combined with `--only`. --update Refresh package metadata and update repositories before applying Also fast-forwards a checkout that `--from` or `--adopt` reuses. Without either, fast-forwards the global config when it is a Git checkout with an upstream, as `--adopt` makes, or links into one, as `--config-dir` makes, then bootstraps from the new commit. Without `--update`, a checkout stays at its current commit. --upgrade Upgrade installed packages and tools as well as installing missing ones In the packages phase, runs the equivalent of `mise bootstrap packages upgrade` after installing; in the tools phase, runs `mise upgrade` (without `--bump`) after installing. Package pins and tool version ranges are respected. Does not update mise itself, repositories, or container images, and does not restart services; see `--update` for repositories and `mise self-update` for mise. -h, --help Print help Examples: Preview every configured part mise bootstrap --dry-run Apply every configured part mise bootstrap Apply only dotfiles and tools mise bootstrap --only dotfiles,tools Apply everything except tools and the bootstrap task mise bootstrap --skip tools,task Replace files that conflict with whole-file dotfile entries mise bootstrap --force-dotfiles Clone a bootstrap project and apply it mise bootstrap --from git@github.com:example/workstation.git Do the same and also load the project's mise.work.toml mise -E work bootstrap --from git@github.com:example/workstation.git Clone a dotfiles repository and link ~/.config/mise to its .config/mise mise bootstrap --from https://github.com/example/dotfiles.git --from-dir ~/.dotfiles --config-dir .config/mise Clone global config into ~/.config/mise, then apply it mise bootstrap --adopt example/mise-config Use a setup repository's dotfile history instead of this machine's mise bootstrap --adopt example/setup --replace-history --yes Refresh package metadata and fast-forward repositories first mise bootstrap --update MISE BOOTSTRAP ACCOUNTS Manage Linux users and groups Creates, updates, or removes the local accounts declared in `[bootstrap.users]` and `[bootstrap.groups]` on Linux. Run `status` or `apply --dry-run` before changing user IDs, group memberships, or account state. Usage: mise bootstrap accounts [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP ACCOUNTS APPLY Create, update, or remove the configured Linux users and groups Usage: mise bootstrap accounts apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP ACCOUNTS STATUS Show the state of the configured Linux users and groups Usage: mise bootstrap accounts status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any account differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP COMPOSE Manage Docker Compose projects from `[bootstrap.compose]` Needs a running Docker engine and the Docker Compose command on this machine. Usage: mise bootstrap compose [OPTIONS] Options: -h, --help Print help Examples: Show the state of every declared project mise bootstrap compose status Show what would change mise bootstrap compose apply --dry-run MISE BOOTSTRAP COMPOSE APPLY Apply Docker Compose projects from `[bootstrap.compose]` Usage: mise bootstrap compose apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP COMPOSE STATUS Show the state of Docker Compose projects from `[bootstrap.compose]` Usage: mise bootstrap compose status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any Compose project differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP FILES Manage system files and directories declared in `[bootstrap]` Applies `[bootstrap.files]` and `[bootstrap.directories]`: paths that need a specific owner, group, or mode, or that must exist or be absent system-wide, such as configuration under /etc. For files in your home directory that you edit, use `[dotfiles]` and `mise dotfiles`. Usage: mise bootstrap files [OPTIONS] Options: -h, --help Print help Examples: Exit with status 1 if any file or directory differs from the config mise bootstrap files status --missing Show what would change mise bootstrap files apply --dry-run Apply without a prompt mise bootstrap files apply --yes MISE BOOTSTRAP FILES APPLY Create, update, or remove the configured system files and directories Usage: mise bootstrap files apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt --prompt-secrets Prompt securely for missing bootstrap secret inputs -h, --help Print help MISE BOOTSTRAP FILES STATUS Show the state of the configured system files and directories Usage: mise bootstrap files status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any file or directory differs from the config (all are still listed) --prompt-secrets Prompt securely for missing bootstrap secret inputs -h, --help Print help MISE BOOTSTRAP FIREWALL Manage the Linux host firewall from `[bootstrap.linux.firewall]` Works with nftables, firewalld, or UFW, and keeps mise's rules separate from other host rules. Over SSH, mise refuses a default incoming policy of deny or reject unless a rule allows the current connection or the config sets `allow_lockout = true`. Check `apply --dry-run` before applying a policy to a remote machine. Usage: mise bootstrap firewall [OPTIONS] Options: -h, --help Print help Examples: Show the firewall's state mise bootstrap firewall status Show the policy and rules that would change mise bootstrap firewall apply --dry-run MISE BOOTSTRAP FIREWALL APPLY Apply the firewall from `[bootstrap.linux.firewall]` Usage: mise bootstrap firewall apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP FIREWALL STATUS Show the state of the firewall from `[bootstrap.linux.firewall]` Usage: mise bootstrap firewall status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if the firewall differs from the config -h, --help Print help MISE BOOTSTRAP LINUX Manage systemd user units from `[bootstrap.linux.systemd.units]` The host firewall in `[bootstrap.linux.firewall]` is managed by `mise bootstrap firewall`. Usage: mise bootstrap linux [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP LINUX SYSTEMD-UNITS Manage systemd user units from `[bootstrap.linux.systemd.units]` Writes unit files to ~/.config/systemd/user, then enables and starts them as configured. An entry with `state = "absent"` is stopped, disabled, and deleted instead. Units run with your permissions and need a reachable systemd user manager. For system units, or a user service that also works on macOS and Windows, use `[bootstrap.services]`. Usage: mise bootstrap linux systemd-units [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP LINUX SYSTEMD-UNITS APPLY Install and start the configured systemd user units Usage: mise bootstrap linux systemd-units apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP LINUX SYSTEMD-UNITS STATUS Show the state of the configured systemd user units Usage: mise bootstrap linux systemd-units status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any unit differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP MACOS Manage macOS preferences and LaunchAgents from `[bootstrap.settings.macos]` and `[bootstrap.macos.launchd]` Usage: mise bootstrap macos [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP MACOS DEFAULTS Manage macOS preferences such as Dock, Finder, and keyboard settings Applies `[bootstrap.settings.macos]`: its `defaults`, `dock`, `finder`, `keyboard`, `trackpad`, and `login_items` tables, and its `[[bootstrap.settings.macos.defaults_entries]]` array of tables. Preferences are written the way `defaults write` writes them. mise does not restart apps: Dock, Finder, and some others show a change only after they relaunch. Other `[bootstrap.settings.]` sections are applied by bootstrap settings plugins through `mise bootstrap settings`. Usage: mise bootstrap macos defaults [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP MACOS DEFAULTS APPLY Write the configured macOS preferences Usage: mise bootstrap macos defaults apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP MACOS DEFAULTS STATUS Show the state of the configured macOS preferences Usage: mise bootstrap macos defaults status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any preference differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP MACOS LAUNCHD-AGENTS Manage macOS LaunchAgents from `[bootstrap.macos.launchd.agents]` Writes each agent to ~/Library/LaunchAgents/dev.mise..plist and loads it into your GUI login session. Run it as the user who owns the agents; an SSH session without a GUI login may not be able to load them. For a user service that also works on Linux and Windows, use `[bootstrap.services]` with `scope = "user"`. Usage: mise bootstrap macos launchd-agents [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP MACOS LAUNCHD-AGENTS APPLY Install and load LaunchAgents from `[bootstrap.macos.launchd.agents]` Usage: mise bootstrap macos launchd-agents apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP MACOS LAUNCHD-AGENTS STATUS Show the state of the configured LaunchAgents Usage: mise bootstrap macos launchd-agents status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any LaunchAgent differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP MISE-SHELL-ACTIVATE Manage mise shell activation from `[bootstrap.mise_shell_activate]` Writes a managed activation block into each configured shell startup file. It does not activate mise in the shell you run it from; open a new shell afterward. Usage: mise bootstrap mise-shell-activate [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP MISE-SHELL-ACTIVATE APPLY Write mise activation into the configured shell startup files Usage: mise bootstrap mise-shell-activate apply [OPTIONS] Options: -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help MISE BOOTSTRAP MISE-SHELL-ACTIVATE STATUS Show the state of the configured shell activation Usage: mise bootstrap mise-shell-activate status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any shell activation differs from the config (all are still listed) -h, --help Print help MISE BOOTSTRAP PACKAGES Manage packages from `[bootstrap.packages]` Declare packages as `"manager:package" = "version"`. `apply` installs what is missing and removes what is declared absent, `use` adds an entry and installs it, and `upgrade` updates configured packages that are installed. `prune` uninstalls Homebrew formulae, casks, or package plugin packages that no config declares. `import` records installed Homebrew formulae, and `status` shows what differs from the config. See https://mise.jdx.dev/bootstrap/packages/ for each package manager. Usage: mise bootstrap packages [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP PACKAGES APPLY Install or remove packages to match `[bootstrap.packages]` Installs each configured package that is missing or does not match its declared version, and removes packages declared `state = "absent"` on the managers that support removal (pacman, scoop, snap, and zypper). On other managers, an installed package declared absent is left in place with a warning; `apply` fails for it only when you pass `--manager` or name the package. Built-in managers may use sudo when not running as root (see the `system_packages.sudo` setting); package plugins never do. Managers that are not available on this machine are skipped. Name packages as `manager:package`, for example `apt:curl` or `brew:jq`, to install them without adding them to config; use `mise bootstrap packages use` to record them as well. When you name packages or pass `--manager`, an unavailable manager is an error instead of a skip. Usage: mise bootstrap packages apply [OPTIONS] [] ... Options: -m, --manager Only apply packages for this built-in or plugin manager -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt --update Refresh package manager metadata first, where the manager supports it For example, apt runs `apt-get update` and dnf adds `--refresh`. brew, brew-cask, flatpak, flatpak-user, macos-app, mas, and snap ignore this flag. -h, --help Print help Arguments: Packages as `manager:package`; defaults to every package in `[bootstrap.packages]` Examples: Install missing packages and remove ones declared absent mise bootstrap packages apply Show what would change mise bootstrap packages apply --dry-run Apply only apt packages, without a prompt mise bootstrap packages apply --manager apt --yes On Debian or Ubuntu, install one package without adding it to config mise bootstrap packages apply apt:curl On macOS, install a formula and a cask without adding them to config mise bootstrap packages apply brew:jq brew-cask:firefox MISE BOOTSTRAP PACKAGES BREW Manage Homebrew tap URLs in `[bootstrap.brew.taps]` mise finds a third-party tap such as `acme/tools` at `https://github.com/acme/homebrew-tools` without an entry. Add one only when the tap's repository lives at a different GitHub URL; only GitHub taps are supported. These commands edit config; they do not run Homebrew. Not available on Windows. Usage: mise bootstrap packages brew [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP PACKAGES BREW TAP Add a Homebrew tap URL to the global `[bootstrap.brew.taps]` Usage: mise bootstrap packages brew tap [OPTIONS] [] Options: -l, --local Write to the local config instead of the global config -n, --dry-run Show the config change without writing it -p, --path, --file Write to this config file or directory -h, --help Print help Arguments: Tap name, e.g. `owner/repo` GitHub URL of the tap; defaults to `https://github.com//homebrew-.git` Examples: Record a tap whose repository is not acme/homebrew-tools mise bootstrap packages brew tap acme/tools https://github.com/acme/brew-tools.git Write the entry to the local config instead mise bootstrap packages brew tap acme/tools https://github.com/acme/brew-tools.git --local MISE BOOTSTRAP PACKAGES BREW UNTAP Remove Homebrew tap URLs from `[bootstrap.brew.taps]` Usage: mise bootstrap packages brew untap [OPTIONS] ... Options: -l, --local Write to the local config instead of the global config -n, --dry-run Show the config change without writing it -p, --path, --file Write to this config file or directory -h, --help Print help Arguments: Tap names, e.g. `owner/repo` Examples: Remove a tap entry from the global config mise bootstrap packages brew untap acme/tools MISE BOOTSTRAP PACKAGES EXPORT Print the configured `nix:` packages as a NixOS module Prints a module that adds each package to `environment.systemPackages`, without running Nix. Import it into a NixOS configuration; packages resolve against that configuration's `pkgs`. Entries for another OS or environment, and entries with `state = "absent"`, are left out. Only shorthand attributes such as `nix:ripgrep` can be exported: a flake reference or a version pin is an error, because the importing configuration decides where packages come from. Usage: mise bootstrap packages export [OPTIONS] Options: --format Output format -h, --help Print help Examples: Write the module to a file you can import from a NixOS configuration mise bootstrap packages export --format nix > packages.nix MISE BOOTSTRAP PACKAGES IMPORT Record installed Homebrew formulae in `[bootstrap.packages]` Adds a `brew:` entry for each linked formula you installed yourself, skipping formulae that were installed only as dependencies; `--all` includes those too. Formulae from third-party taps are written with their full name, and each tap gets a `[bootstrap.brew.taps]` entry with the URL already in your config or the default GitHub URL. Writes the local config unless you pass `-g`, `-e`, or `-p`. Usage: mise bootstrap packages import [OPTIONS] Options: -e, --env Write to the config file for this environment (mise..toml) -g, --global Write to the global config (~/.config/mise/config.toml) New entries go to the `write_targets.packages` file when that setting is set. -m, --manager Package manager to import from Default: brew --all Import every linked formula, including dependencies -n, --dry-run Show the entries that would be written without writing them -p, --path, --file Write to this config file or directory -h, --help Print help Examples: Show the entries that would be written mise bootstrap packages import --dry-run Write them to the local config mise bootstrap packages import Include formulae installed as dependencies mise bootstrap packages import --all Write to the global config mise bootstrap packages import -g MISE BOOTSTRAP PACKAGES PRUNE Uninstall packages that no config declares For `brew` (the default), removes every linked formula that is neither declared nor needed by a declared formula or cask, including formulae you installed with Homebrew itself. Run with `--dry-run` first, or record existing formulae with `mise bootstrap packages import`. For `brew-cask`, removes only casks mise installed and can prove are unchanged. For a package plugin that supports uninstalling, removes only packages mise installed. A package is kept while the current config, or any trusted config mise has tracked, still declares it. Usage: mise bootstrap packages prune [OPTIONS] Options: -m, --manager Package manager to prune: `brew`, `brew-cask`, or a package plugin Default: brew -n, --dry-run Show what would be removed without removing anything -y, --yes Skip the confirmation prompt --force Remove `brew-cask` casks that mise installed even when it cannot prove they are unchanged, such as self-updating apps or casks with install scripts mise removes the files it recorded installing that are still in place, but not what a cask's own install scripts created. -h, --help Print help Examples: Preview which Homebrew formulae would be removed mise bootstrap packages prune --dry-run Remove them without a prompt mise bootstrap packages prune --yes Preview which casks would be removed mise bootstrap packages prune --manager brew-cask --dry-run Preview removals for a package plugin named vscode mise bootstrap packages prune --manager vscode --dry-run MISE BOOTSTRAP PACKAGES STATUS Show the state of packages from `[bootstrap.packages]` Usage: mise bootstrap packages status [OPTIONS] Options: -J, --json Output in JSON format --missing Exit with status 1 if any package differs from the config (all are still listed) -h, --help Print help Examples: List every configured package and its state mise bootstrap packages status Print the state as JSON mise bootstrap packages status --json Exit with status 1 if any package differs from the config mise bootstrap packages status --missing MISE BOOTSTRAP PACKAGES UPGRADE Upgrade installed packages from `[bootstrap.packages]` Refreshes package manager metadata, then upgrades the configured packages that are already installed. Each manager decides which version is current. Version pins in config are honored where the manager can install them; other pinned entries are skipped with a warning. Packages that are not installed yet are skipped; install them with `mise bootstrap packages apply`. See https://mise.jdx.dev/bootstrap/packages/ for what each manager does. Name packages as `manager:package` to upgrade only those. Usage: mise bootstrap packages upgrade [OPTIONS] [] ... Options: -m, --manager Only upgrade packages for this built-in or plugin manager -n, --dry-run Show what would change without changing anything -y, --yes Skip the confirmation prompt -h, --help Print help Arguments: Packages as `manager:package`; defaults to every package in `[bootstrap.packages]` Examples: Show what would be upgraded mise bootstrap packages upgrade --dry-run Upgrade every configured package that is already installed mise bootstrap packages upgrade Upgrade only apt packages, without a prompt mise bootstrap packages upgrade --manager apt --yes Upgrade one Homebrew formula mise bootstrap packages upgrade brew:postgresql@17 MISE BOOTSTRAP PACKAGES USE Add packages to `[bootstrap.packages]` and install them Like `mise use` for tools: writes a `"manager:package" = "version"` entry to the local mise.toml (or the global config with `-g`), then installs anything missing. If the manager is not available on this machine, such as `apt:` on macOS, the entry is written without installing. Pin a version with `@`, as in `apt:curl@8.5.0-2`; without `@`, or with `@latest`, the entry is `"latest"`. Homebrew puts versions in formula and cask names (`brew:postgresql@17`, `brew-cask:temurin@17`), so there `@` is part of the name. mas takes numeric App Store IDs and nix takes attribute paths or flake references, so neither accepts `@version`. aur, flatpak, flatpak-user, pacman, and snap accept `@version` but cannot install a pin, so installing skips those entries with a warning. Usage: mise bootstrap packages use [OPTIONS] ... Options: -e, --env Write to the config file for this environment (mise..toml) -g, --global Write to the global config (~/.config/mise/config.toml) instead of the local one New entries go to the `write_targets.packages` file when that setting is set. -n, --dry-run Show what would change without writing config or installing -p, --path, --file Write to this config file or directory -y, --yes Skip the confirmation prompt --no-install Write the package declarations without checking or installing packages -h, --help Print help Arguments: Packages in `manager:package[@version]` form Examples: Declare apt and winget packages; each machine installs the ones it can mise bootstrap packages use apt:curl winget:BurntSushi.ripgrep.MSVC On macOS, add a formula and a cask mise bootstrap packages use brew:jq brew-cask:firefox Add a versioned Homebrew formula to the global config mise bootstrap packages use -g brew:postgresql@17 Pin an apt package to a version mise bootstrap packages use apt:curl@8.5.0-2 MISE BOOTSTRAP PACKAGES WHERE Print the `opt` path of an installed Homebrew formula Prints a path such as /opt/homebrew/opt/openssl@3 that keeps pointing at the installed version across upgrades. Name the formula as `brew:` or `brew://`, using its installed name; aliases are not resolved, and a tap-qualified name matches by formula name only. The command does not read mise config files, so only environment variables and global flags apply. If the formula is not installed, it prints nothing and exits with a nonzero status. Works on macOS on Apple silicon and on Linux (x86_64 and arm64). Usage: mise bootstrap packages where [OPTIONS] Options: -h, --help Print help Arguments: Formula to locate, as `brew:` or `brew://` Examples: Put a formula's bin directory on PATH when it is installed if root="$(mise bootstrap packages where brew:unzip)"; then export PATH="$root/bin:$PATH" fi MISE BOOTSTRAP PLAN Show what applying bootstrap resources would change Covers accounts, packages, files and directories, system and user services, the firewall, Compose projects, and Git repositories, in dependency order. Hooks are listed with the action `run`, since a command cannot be diffed; they do not count as changes for `--detailed-exitcode`. Dotfiles, shell activation, macOS defaults, LaunchAgents, systemd user units, the login shell, tools, and the `bootstrap` task are not planned; preview the whole run with `mise bootstrap --dry-run`. Usage: mise bootstrap plan [OPTIONS] Options: -J, --json Output a stable machine-readable plan in JSON format --detailed-exitcode Exit 0 if nothing would change, 2 if something would, 1 on errors or unknown state A resource's state is unknown when mise cannot reach its declared state on its own, for example a package whose manager is not available on this machine or cannot install the pinned version, or a service whose unit does not exist. --prompt-secrets Prompt securely for missing bootstrap secret inputs -h, --help Print help Examples: Show the planned changes mise bootstrap plan Print the plan as JSON mise bootstrap plan --json Exit with status 2 if anything would change mise bootstrap plan --detailed-exitcode MISE BOOTSTRAP PLUGINS Manage package manager plugins declared in `[bootstrap.plugins]` A package plugin adds a package manager, such as one for VS Code extensions, that `[bootstrap.packages]` entries can use. `mise bootstrap` installs plugins before packages; when you run the narrower commands, run `plugins apply` before `packages apply`. Installing a plugin does not install its packages. Usage: mise bootstrap plugins [OPTIONS] Options: -h, --help Print help MISE BOOTSTRAP PLUGINS APPLY Install package manager plugins declared in `[bootstrap.plugins]` It does not ask for confirmation. Usage: mise bootstrap plugins apply [OPTIONS] Options: -n, --dry-run Show which plugins would be installed without installing them -h, --help Print help MISE BOOTSTRAP PLUGINS STATUS Show whether declared package manager plugins are installed Usage: mise bootstrap plugins status [OPTIONS] Options: --missing Exit with status 1 if a declared plugin is not installed -h, --help Print help MISE BOOTSTRAP REMOTE Bootstrap one or more machines over SSH Packs a local project directory, copies it to each target, stages mise there, and runs `mise bootstrap`. The directory is `--source`. Without it, an inventory host uses its own `source`, then the one in `[bootstrap.remote]`, then the current directory; a `--host` target uses the current directory. Pick targets by name, `--tag`, or `--all` from `[bootstrap.remote.hosts]`, or give any SSH destination with `--host`. Targets need a POSIX shell plus `tar`, `mktemp`, `cksum`, and `uname`; Windows targets are not supported. `--dry-run` still connects, uploads, and inspects each target, but changes nothing there. With `--adopt`, each target adopts the repository as `mise bootstrap --adopt` does, instead of receiving a project directory. The `--github-relay-*` flags let targets read private GitHub repositories through this machine's credentials for the length of the run, without copying a token to them. See https://mise.jdx.dev/bootstrap/github-relay.html. Usage: mise bootstrap remote [OPTIONS] [] ... Options: --adopt Adopt global configuration or shared dotfile history on each target --all Select every inventory host --bootstrap-command Shell command, run on each target, that installs mise and puts it on PATH --connect-timeout SSH connection timeout in seconds Default: 10 --copy-link Copy the target of this source-relative symbolic link instead of the link; repeat for more --copy-links Copy the targets of every symbolic link in the source instead of the links --exclude Another pattern to leave out of the archive; repeat for more --fail-fast Stop after the first failed target --force-dotfiles Overwrite files on each target that conflict with whole-file dotfile entries --host <[USER@]HOST> SSH destination that is not in the inventory (`[user@]host`); repeat for more -i, --identity-file SSH identity file, overriding the inventory and SSH config -n, --dry-run Show what would change on each target without changing it It still connects to each target, uploads the project, stages mise, and inspects the target. --install-mise Install the provisioned mise on each host instead of only staging it Defaults to `~/.local/bin/mise`; pass `--install-mise=` for another path. --keep-staging Keep the remote staging directory for debugging --mise-bin Upload this local mise executable, for platforms without an official release binary --no-install-mise Do not install mise on the host, even when the selected hosts configure it --only Run only these parts on each target Repeat the flag or separate parts with commas. Cannot be combined with `--skip`. --port SSH port, overriding the inventory and SSH config --prompt-secrets Prompt securely for missing secret inputs on the remote host --remote-env Config environments to load on each target; repeat or separate with commas (for example, ci,dotfiles) --remote-mise Existing mise executable name or path; relative paths use the staged project --skip Skip these parts on each target Repeat the flag or separate parts with commas. Cannot be combined with `--only`. --source Local directory to archive and send to each target --ssh-option