Mise — Dev Environment Manager for Any Language

What it is

Mise is a development environment manager that handles version management for Node, Python, Go, Rust, Java, and 100+ other tools through a single CLI. It replaces the collection of version managers (nvm, pyenv, rbenv, sdkman) that developers typically install and maintain separately.

Mise uses a .mise.toml file for project-level version pinning. When you cd into a project directory, Mise automatically activates the correct versions of all tools. It also supports .tool-versions (asdf format) and .node-version files for backward compatibility.

How it saves time or tokens

Mise eliminates the overhead of installing and configuring multiple version managers. Instead of learning the syntax for nvm, pyenv, and rbenv separately, you use one consistent CLI. Switching between projects with different Node and Python versions is automatic.

The estimated token cost for a typical Mise configuration is around 2,600 tokens. This small upfront investment pays off by preventing version mismatch bugs and onboarding delays.

How to use

1. Install Mise:

curl https://mise.run | sh

1. Install tools and pin versions:

mise use node@20
mise use python@3.12
mise use go@1.22

1. This creates a .mise.toml in your project:

[tools]
node = "20"
python = "3.12"
go = "1.22"

Example

A full-stack project with multiple tools:

# .mise.toml
[tools]
node = "20.12"
python = "3.12"
go = "1.22"
rust = "1.77"
java = "21"

[env]
DATABASE_URL = "postgres://localhost/myapp"

[tasks.dev]
run = "npm run dev"
description = "Start development server"

[tasks.test]
run = "npm test && go test ./..."
description = "Run all tests"

Mise also manages environment variables and custom tasks, replacing both version managers and simple task runners.

Related on TokRepo

• AI tools for coding -- Development tools and environment management
• Automation tools -- Tools for automating development workflows

Common pitfalls

• Forgetting to activate Mise in your shell. Add eval "$(mise activate zsh)" (or bash/fish) to your shell profile. Without activation, version switching does not happen automatically.
• Conflicting with existing version managers. If nvm and Mise both manage Node, they may fight over PATH priority. Remove or disable nvm before switching to Mise.
• Not committing .mise.toml to the repository. The file should be version-controlled so all team members use the same tool versions. Add mise trust in your onboarding docs.