Doesn't respect $XDG_CONFIG_HOME nor even $MISE_CONFIG_DIR

[ccjmne]

Not too sure what is going on here.

It supposedly respects the XDG paths spec: https://mise.jdx.dev/directories.html

But I don't see it function in practice. In addition, the $MISE_CONFIG_DIR override is documented, but seems to have no effect either.

> mise --version
              _                                        __
   ____ ___  (_)_______        ___  ____        ____  / /___ _________
  / __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
 / / / / / / (__  )  __/_____/  __/ / / /_____/ /_/ / / /_/ / /__/  __/
/_/ /_/ /_/_/____/\___/      \___/_/ /_/     / .___/_/\__,_/\___/\___/
                                            /_/                 by @jdx
2025.11.3 linux-x64 (2025-11-10)


> export MISE_CONFIG_DIR=$XDG_CONFIG_HOME/mise
> cat $MISE_CONFIG_DIR/config.toml
[tools]
java = "temurin-21"
maven = "latest"
node = "latest"

[settings]
idiomatic_version_file_enable_tools = ["node"]

[env]

; mise config list
Path  Tools

[TzeroOcne]

I have similar problem but instead of not detecting the config it keep detecting the default global config at ~/.config/mise/config.toml which based on the documentation I think it should not, I don't know if it's the same problem or not and not sure if it's the intended behavior

zsh> mise --version
              _                                        __
   ____ ___  (_)_______        ___  ____        ____  / /___ _________
  / __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
 / / / / / / (__  )  __/_____/  __/ / / /_____/ /_/ / / /_/ / /__/  __/
/_/ /_/ /_/_/____/\___/      \___/_/ /_/     / .___/_/\__,_/\___/\___/
                                            /_/                 by @jdx
2025.12.3 windows-x64 (2025-12-13)
zsh> echo $MISE_CONFIG_DIR
/c/Users/tzero/.local/app-extras/obs
zsh> mise config
Path                                              Tools
C:/Users/tzero/.local/app-extras/obs\mise.toml    python
C:/Users/tzero/.local/app-extras/obs\config.toml  python
C:\Users\tzero\.config\mise\config.toml           go, gum, neovim, python, uv

[risu729]

#7271 fixed.

[JamBalaya56562]

The reading half of this was fixed by #7271, as @risu729 noted. The writing half stayed broken until now, and it failed silently, so it is worth closing the loop here.

With MISE_CONFIG_DIR relocated, mise use could still choose ~/.config/mise/config.toml as its write target — the very file #7271 stops mise from loading — and write the tool there. mise config ls then correctly refused to list it, so the tool simply never appeared, with no error anywhere.

The cause was that mise had three separate implementations of the same "which config file do I write to" rule, and only one of them applied the exclusion added for this discussion. Two changes put them on the same footing:

• fix(config): don't pick a write target that config loading ignores #11571 — the two resolvers that walk up from the cwd now share a single implementation, which applies the exclusion.
• fix(config): apply ignore filters to --path <dir> write targets #11609 — mise use --path <dir> and mise set --file <dir> resolve to a file inside the named directory, and that lookup was not applying it either. Excluded candidates are now skipped when choosing, so an excluded mise.toml sitting next to a live mise.local.toml picks the latter; when nothing in the directory is loadable it still creates the default name — you named that directory explicitly — but says so rather than writing in silence. mise unuse --path resolves through the same function and is fixed with it.

Both merged 2026-08-02. Reproduced beforehand on v2026.7.15 and v2026.7.18, on Linux and Windows.

Not in a release yet — v2026.8.0 was cut a few hours before they merged, so they land in the next one.

One thing worth recording for anyone arriving here from a search: ignored_config_paths is what produces the silent case. The persisted ignore list (mise trust --ignore) cannot — it is overridden by trusted_config_paths, and without that override the write fails the trust check loudly instead of landing somewhere unread.

[ccjmne]

Ah, thank you so much!

Seeing as such a simple, obvious, ubiquitous, documented feature was completely missing, and that the subsequent fix was utterly inadequate, I'd stopped using Mise altogether. Having quite evidently just about nobody care about any of this even among its user community also does raise some eyebrows: what do the serious people use?

However, I quite like the $path manipulation rather than the use of shims... and the recipes being presumably largely more certifiable. If only mise activate could take no more than 1 or 2 milliseconds instead of well over 20, I would be happy to give it another chance.
That and, of course, the completion system having been broken for years on Zsh. And the near-daily releases of mostly pointless churn, vibe-coded, vibe-reviewed, but not even vibe-tested, as this tread quite empirically proves.

But mostly what remains is the unacceptably long start-up time.

[jdx]

good riddance, jesus christ