working-with-mise

Mise manages per-project tool versions by storing them in mise.toml files at your project root. Run `mise use <TOOL@VERSION>` to install and configure a tool, then commit the config file so team members get the same versions automatically.

Mise requires shell activation to add tools to your PATH. Run `mise activate` to enable it in your shell, or use `mise doctor` to diagnose missing activation and configuration issues.

Shell activation exposes mise-managed tools in your PATH. Run `mise activate` and follow the guidance for your shell type, or use `mise doctor` to detect your configuration and recommend the correct activation method.

Mise works with tools that have published versions. Use `mise who` or `mise doctor` to check tool availability and whether mise is the right fit for your specific dependency before investing in setup.

Always use `mise use <TOOL@VERSION>` to modify tool configurations—it updates mise.toml correctly and ensures consistency. The iron rules prevent manual editing errors and activation failures.

Run `mise doctor` to scan for configuration problems, PATH issues, and activation errors. Use `mise who` to inspect tool detection, then apply fixes to activation or config rather than creating workarounds.