To install mise on Ubuntu 26.04 or 24.04, use the official installer: curl -fsSL https://mise.run | sh. It installs mise for your user account. You can also use APT through extrepo on either release, or the official PPA on Ubuntu 26.04 and newer.
mise manages development tools, project environment variables and repeatable tasks. You can keep a personal Node.js default while each project selects its own version. Below, you will set up your shell and run a small project. If a step fails, leave a comment with the error or contact us.
Before you begin
- Ubuntu 26.04 LTS or 24.04 LTS, internet access and a terminal. On Ubuntu Desktop, press Ctrl+Alt+T.
- You need curl and trusted CA certificates for the installer. Use sudo for Ubuntu packages, then run mise and project commands as your normal user.
- The main steps use Bash. Zsh activation is provided separately; Zsh must already be installed if you choose it.
- Choose only one installation method per system. A user-local binary and an APT binary can conflict on PATH. If mise is already installed, identify its source before continuing.
Install the download prerequisites first:
sudo apt update && sudo apt install -y curl ca-certificates
The installer downloads and executes code from the mise project. Use it only if you trust that source. An inspection option is included below.
1. Install mise with the Official Script
Step 1: Check your Ubuntu release and existing installations
Check the release, commands already on PATH and the usual script-install location:
cat /etc/os-release
type -a mise
ls -l ~/.local/bin/mise
A command-not-found message and a missing file are normal on a fresh system. If either check finds mise, stop and check how it was installed. Do not add an APT copy over an existing script install.
Step 2: Run the installer
Use this method on either Ubuntu release. Do not run it with sudo:
curl -fsSL https://mise.run | sh
The default executable is ~/.local/bin/mise. The installer does not give you automatic tool switching until you activate mise in your shell.
To inspect the script first, use this alternative instead of the one-line installer. The unique temporary file avoids overwriting a file you already have. Read it with less, press q to exit, and run it only if you accept its contents:
mise_installer=$(mktemp) && curl -fsSL https://mise.run -o "$mise_installer" && less "$mise_installer"
After reviewing it in the same terminal:
These are two ways to run the same installer, not separate installation methods. The upstream mise installation guide documents the script and APT options.
2. Alternative: Install mise with APT
Skip this section if you used the script. APT installs the mise executable system-wide, while development tools and personal settings still belong to your user account. Choose one of the following repository routes.
Option A: extrepo on Ubuntu 24.04 and 26.04
extrepo enables the upstream mise repository and manages its repository configuration. Refresh your Ubuntu package lists first, then run:
sudo apt update &&
sudo apt install -y extrepo &&
sudo extrepo enable mise &&
sudo apt update &&
sudo apt install -y mise
The chained commands stop if a step fails. Do not add the PPA as well. You do not need to copy legacy manual keyring commands.
Option B: Official PPA on Ubuntu 26.04 and newer
Use this alternative only on Ubuntu 26.04 or newer. Ubuntu 24.04 users should choose extrepo or the script. Install the repository helper if needed:
sudo apt update && sudo apt install -y software-properties-common
Next, enable the official PPA and install mise:
sudo add-apt-repository -y ppa:jdxcode/mise &&
sudo apt update &&
sudo apt install -y mise
Continue with the APT-specific activation commands below.
3. Activate mise in Bash or Zsh
Activation lets mise select tools when you enter a project directory. Add the hook once, in the startup file for the shell you actually use. You can check your current shell with ps -p $$ -o comm=.
Bash: Script installation
Use the full executable path because ~/.local/bin may not be on PATH yet:
echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
source ~/.bashrc
This appends the hook without replacing your existing Bash configuration. You can open a new terminal instead of sourcing the file. Do not repeat the echo command each time you open a terminal.
Bash: APT installation
If APT installed mise, use its command name:
echo 'eval "$(mise activate bash)"' >> ~/.bashrc
source ~/.bashrc
Zsh: Use ~/.zshrc instead
For a script installation, run these commands from Zsh:
echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
source ~/.zshrc
For an APT installation, use this alternative:
echo 'eval "$(mise activate zsh)"' >> ~/.zshrc
source ~/.zshrc
Do not source ~/.bashrc from Zsh or add both shell variants to the same startup file.
Verify the setup
After activation, check mise and read its diagnostics:
mise --version
mise doctor
The first command prints your installed version. The second checks your environment and reports issues such as missing activation. Resolve reported errors before adding tools. Exact version numbers will change. See the official shell setup guide for other shells and editor environments.
For Python project dependencies, our uv guide for Ubuntu covers virtual environments, package installation and lockfiles. Decide which tool selects Python for a project so mise and uv do not choose different interpreters unexpectedly.
4. Set a Global Development Tool Default
Step 1: Install Node.js 24 for your account
Set the default Node.js major version:
mise use --global node@24
node --version
npm --version
mise installs a matching Node.js 24 release and records the request in ~/.config/mise/config.toml on a default setup. Node.js includes npm. Expect a Node version starting with v24.; the patch number depends on the available release.
Here, global means your personal default, not a replacement for Ubuntu system packages or a setting for every user. A project can override it. Do not use sudo with mise use.
You can manage Python and Go with the same pattern, for example mise use --global [email protected] or mise use --global [email protected], when those are the versions your work needs. These are optional examples, not additional prerequisites. Leave Ubuntu’s system Python in place.
5. Create a Project with mise.toml
Step 1: Make a new practice folder
Create a unique folder under your home directory, then stay in it for the following steps:
mise_demo_dir=$(mktemp -d "$HOME/mise-demo.XXXXXX") && cd "$mise_demo_dir"
pwd
Using a new directory keeps the example from overwriting an existing project. Keep this terminal open; pwd prints the folder to return to later.
Step 2: Add tools, environment variables and tasks
While inside the new practice folder, create mise.toml. The command below writes this file; do not use it over an existing configuration you need to keep:
cat > mise.toml <<'TOML'
[tools]
node = "24"
[env]
APP_NAME = "Ubuntu mise demo"
[tasks]
hello = "node hello.js"
check = "node --check hello.js"
TOML
The [tools] section selects Node.js 24 for this directory. [env] defines a non-secret value for the project. [tasks] gives names to commands you will run repeatedly. TOML uses section names in square brackets and quoted string values.
The "24" request allows matching 24.x releases; it is not an exact patch pin. For an exact version, use mise use --pin node@24 in the project and review the resulting change before committing it. See the mise.toml reference for configuration precedence.
Step 3: Add a small JavaScript file
Create the greeting program in this same practice folder:
cat > hello.js <<'JS'
console.log(`Hello from ${process.env.APP_NAME}!`);
console.log(`Node version: ${process.version}`);
JS
The program reads the environment variable from mise.toml and prints the actual Node.js version. It has no npm dependencies.
Step 4: Review, trust and install
Configuration files can run code through tasks or other settings. Review files from other people before trusting them. If mise reports that this configuration is untrusted, trust the reviewed file, then install its tools:
Run these inside the practice directory. mise trust approves the configuration; it is not a malware scan. mise install installs tools requested by the loaded configuration. It does not install npm project dependencies.
With an activated shell, entering this directory selects its configured Node.js version. Leaving it restores your personal defaults unless another parent configuration applies. Commit mise.toml with your project when teammates should share its setup. Do not commit passwords or API tokens in the environment section.
For a compiled-language project, our Mojo setup guide for Ubuntu shows how to install the compiler in a Pixi environment, run a program and build an executable. Keep that project’s compiler dependencies in Pixi; the mise tasks above do not install Mojo.
6. Run Tasks and Commands without Activation
Run the named tasks
From the project folder, run the syntax check and greeting:
mise run check
mise run hello
The check should finish successfully without a JavaScript syntax error. The hello task prints the greeting and a Node version starting with v24. Tasks run with the configured tools and project environment. See TOML tasks for task descriptions and dependencies.
Hello from Ubuntu mise demo!
Node version: v24.x.x
The output above uses x as a patch-number placeholder. Your terminal prints the installed version.
Run one command with mise exec
To run a command with the project environment explicitly:
mise exec -- node hello.js
This is useful in scripts and CI because it does not need an interactive shell activation hook. It reads the configuration for your current working directory. The double hyphen separates mise options from the command to run.
The mise executable itself must still be reachable. For a script install where ~/.local/bin is missing from PATH, use the absolute home-relative path, from the project directory:
~/.local/bin/mise install
~/.local/bin/mise exec -- node hello.js
Trust the reviewed project first if prompted. In CI, install mise and the requested tools as part of setup; mise exec does not make an unknown project safe. See the exec reference.
7. Update mise and Its Managed Tools
Script install: Update the mise program
Use this for the mise.run installation. Do not use sudo or run self-update on an APT-owned executable.
APT install: Use Ubuntu package updates
sudo apt update && sudo apt upgrade
This updates installed packages with available upgrades, including mise from your enabled repository. Review APT’s proposed changes. To request only the mise package upgrade, use sudo apt install --only-upgrade mise after refreshing package lists.
Update the tools managed inside mise
In a project directory, preview tool changes first:
Then apply the changes you accept:
This updates configured development tools within their requested ranges, not the mise executable. With node = "24", the range remains 24.x. Test your project after an update. Use mise upgrade --global for personal defaults independently of the current project. See upgrade behavior.
8. Fix Common mise Problems
Issue 1: mise: command not found
For a script installation, check the binary directly:
~/.local/bin/mise --version
If that works, use the full-path activation hook from Section 3 and reload the correct shell. If the file is missing, check whether installation failed before rerunning it. An APT installation should expose the command through /usr/bin.
Issue 2: The wrong Node.js version runs
type -a mise
type -a node
mise ls
mise doctor
Run these inside the project directory. Check the project and parent configurations, then check shell startup order. A second version manager or a later PATH assignment can take priority. Keep one manager in control of Node.js in that shell; do not delete Ubuntu packages to repair a shell hook.
Issue 3: An untrusted configuration blocks commands
Read mise.toml and any referenced files. If you trust the configuration, run mise trust in its directory and retry mise install. Do not approve an unfamiliar repository merely to suppress the warning.
Issue 4: APT cannot find mise or a repository fails
Check that you enabled exactly one repository route and that sudo apt update completed successfully. On Ubuntu 24.04, use extrepo rather than the 26.04+ PPA. Read certificate, network or signing errors before trying again; do not disable signature checks.
Issue 5: A task cannot find hello.js
Return to the practice folder printed by pwd. Check that both mise.toml and hello.js exist, with matching capitalization. If you opened a new terminal, change back to that directory before running the tasks.
Resume after a failed install
Fix the reported network, permission or repository error first. Once the mise executable works, return to the reviewed project folder and run mise install again. It can install the requested tools that are still missing. Check the result with mise doctor, then retry mise run check. Do not rerun every installation method.
9. Uninstall mise and Clean Up
Back up settings and check which projects rely on mise before removing it. Removing managed tools can stop those projects from running. Use the branch for your installation method. The paths below assume mise’s default directories; custom MISE_* or XDG paths need separate review.
Step 1: Inspect and remove your shell hook
Find the activation line in the startup file you edited:
grep -n "mise activate" ~/.bashrc
Open ~/.bashrc in your text editor and remove only the eval "$(...mise activate bash)" line you added. For Zsh, inspect and edit ~/.zshrc instead. Do not delete the whole startup file. Keep the current terminal open until cleanup is finished, then open a fresh terminal.
Step 2A: Remove a script installation
Preview the removal before accepting it:
This lists the executable, installed tools and other data that would be removed. Current mise also considers its shared system data directory, normally /usr/local/share/mise. Stop if the preview includes shared resources other people need. Do not add sudo to force their removal.
For your reviewed personal installation, choose one of these commands. Keep the interactive prompts so you can review each removal. To retain the personal configuration directory:
Or, to remove the personal configuration directory as well:
The second command also deletes your global defaults and other mise settings. Project-local files such as mise.toml and hello.js need separate review; do not assume they have been deleted. See the implode removal reference.
Step 2B: Remove an APT installation
Use APT rather than mise implode for an APT-owned executable:
Purging the package does not remove your user-owned tool installations or personal settings.
Optional APT user-data cleanup
The following command permanently deletes your mise-managed tools and personal configuration. Back up anything you want to keep, confirm these are the directories you use, and do not run it with sudo:
rm -rI -- "$HOME/.local/share/mise" "$HOME/.config/mise"
The uppercase -I asks for confirmation before recursive removal. A missing-directory message is harmless. This covers the default tool-data and configuration directories; cache and state can also remain at ~/.cache/mise and ~/.local/state/mise. Inspect those folders and remove only mise data you no longer need. Project files stay in their project directories.
If you also want to disable the APT source, choose the command for the route you enabled. For extrepo:
sudo extrepo disable mise
sudo apt update
For the PPA on Ubuntu 26.04+:
sudo add-apt-repository --remove -y ppa:jdxcode/mise
sudo apt update
You can leave extrepo and software-properties-common installed; other repositories may use them. Open a fresh terminal after removing the hook and executable. type -a mise should find no mise command unless another installation remains.
Helpful Resources
Frequently Asked Questions
Does mise work on Ubuntu 24.04 and 26.04?
The official script and extrepo APT route support both releases. The official PPA route documented here is for Ubuntu 26.04 and newer. Tool availability also depends on the tool and your CPU architecture.
Should I install mise with both curl and APT?
No. Choose one installation method. Two mise executables can compete on PATH, and each method has a different update and removal process.
What is the difference between global and project tool settings?
A global setting is a default for your user account, normally stored in ~/.config/mise/config.toml. A project mise.toml can choose its own tools and environment when you work in that directory.
Can I use mise without activating my shell?
Yes. Run mise exec — followed by the command, from the project directory. mise must still be installed and reachable; use ~/.local/bin/mise explicitly after a script install if that directory is missing from PATH.
Does mise install also install npm dependencies?
No. mise install installs development tools requested by your configuration. For an npm project, install its packages separately using the project instructions, such as npm ci when it has a valid package-lock.json.
Does mise upgrade update the mise program itself?
No. mise upgrade updates configured development tools. Use mise self-update for a script-installed mise executable, or APT updates for an APT installation.
More Ubuntu development guides: Set up Visual Studio Code · Install and use TypeScript · Install and use Go
Views: 125