Tool remains on path if MISE_DISABLE_TOOLS is set through mise

[proceduralnoisy]

This bug occurs on 2026.5.6 on both Linux and Windows

Consider the following:

# Use and install node via mise
mise use node
# Disable node in the same directory
mise set MISE_DISABLE_TOOLS="node"

mise is correctly ignoring node when running mise list, but mise incorrectly continues to add node to the path.

Observations:

• The incorrect behavior occurs even after running mise reshim or relaunching the shell.
• • Calling mise uninstall node resolves the issue, but the issue returns if the tool is reinstalled (e.g. in another directory that uses it)
• It works correctly if MISE_DISABLE_TOOLS is set in a parent directory instead (this only occurs when it's disabled in the same directory that uses the tools)
• It works correctly if the disable_tools setting is used instead

Use case:
We have a Python-based CLI tool that is installed by mise, but occasionally need to redirect to the system version of the tool (specifically, to test against an editable version of the tool, which mise doesn't currently seem to support).

In the past, we could use mise use --env local pipx:mytool@system, but the @system functionality is now deprecated.

Any alternative suggestions would be appreciated!

[risu729]

Why don't you set as a setting?

mise reads the env var from the process and it won't get overridden by the env var set in the config. If this is not documented I think we should.

[proceduralnoisy]

That would work, but it would be ideal if our users could 'opt in' to this override on a repo-by-repo (i.e. folder-by-folder) basis. We often have many cloned repos using different versions of our tool, and only need to redirect one or two to use an editable package.

mise reads the env var from the process and it won't get overridden by the env var set in the config. If this is not documented I think we should.

If that's a fundamental limitation, then perhaps we're stuck. But it does seem that some parts of mise are considering the env var in the config, since mise ls correctly excludes the disabled tool.

Personally, I was a fan of mise use tool@system, so it was unfortunate to see that useful feature get deprecated.

[jdx]

That would work, but it would be ideal if our users could 'opt in' to this override on a repo-by-repo (i.e. folder-by-folder) basis.

you can do this with settings

[proceduralnoisy]

Ah, nice. I had always assumed settings were only supported in the global config. It looks like doing mise settings add --env local disable_tools node works as expected for our use case.

This bug is no longer a blocker for our use case. The current behavior might be unexpected/surprising for others, so I'll leave it open.

Thanks for your help!