Mise 2026.10 release introduces LSP and container daemons

The October 2026 release of mise (v2026.10.18) introduces mise lsp, a language server for mise config files. The mise lsp provides diagnostics, completion, hover, navigation, and quick fixes for mise.toml files. It detects TOML syntax errors, unknown keys with "did you mean" suggestions, and deprecated keys. The tool also warns about task references that point to no task and reports dependency cycles as errors. It only handles files that mise loads as configs, such as mise.toml or conf.d/*.toml files. This functionality integrates with editors like Neovim, Helix, Emacs, Zed, and VS Code. This release arrives as Rust-based tooling goes mainstream in the JavaScript ecosystem, following the unification of Vite, Vitest, Oxc, and Rolldown under VoidZero.

You already know the basics of polyglot version managers, but this LSP adds deep configuration intelligence. Hovering over a line shows the description and backends of a tool or the description and command of a task. Navigation allows users to go to a task’s definition, find its references, or rename a task along with every reference in the file. The tool also provides quick fixes to replace unknown keys or task names.

Container daemons and orchestration

Experimental daemons in the mise-en-place 2026.10.24 release allow users to run container images using Docker or Podman. These daemons support ports, readiness checks, dependencies, and the proxy. Every port publishes to 127.0.0.1 only to keep services private. Containers receive names based on the project and worktree so that two checkouts never clash. The runtime defaults to Docker if it is on the PATH, otherwise it uses Podman. However, starting a container daemon on Windows fails.

For daemon presets, named ports like http_port now accept auto, base, or stride configurations. Each linked worktree adds its slot to the port’s own base. The data_mount feature bind-mounts a per-checkout data directory. Users can use the ready_cmd placeholder within the configuration to execute commands like docker exec. Mise does not pull or build images or start the Docker/Podman service, and it only supports TCP ports.

Version precision and stability

Mise manages version precision through the mise upgrade –bump –pin command. This command writes resolved versions directly to the configuration file. For example, a request for version 22 becomes 22.1.0. If the MISE_PIN=1 setting is active, a plain mise upgrade –bump performs this exact version rewrite. This control helps developers avoid the unpredictability of fuzzy version requests. For Python users, mise lock for pypi: tools now accepts PyPI simple indexes that respond with a PEP 691 +html content type. This supports registries like Azure Artifacts. For Ruby users, gem installs and bundle install no longer fail when mise is not on the PATH.

The October 12, 2026, incident on GitHub occurred because a latent condition in the notifications delivery pipeline sent a high volume of an expensive query to sharded database replicas, reducing available capacity for Issues and Pull Requests. The October 22, 2026, outage also caused intermittent errors loading Issues and Pull Requests. These disruptions complicate workflows for developers who rely on GitHub-hosted tools. The mise 2026.10 release transforms the tool from a simple version manager into a comprehensive orchestration engine. Will the integration of container daemons eventually replace standalone orchestration tools for local development?