warnings for global tools on every mise call when locked=true

[bs-va]

With these conditions

• I have usage@latest installed globally
• my project has settings.locked = true

I'm getting this warning every time mise is called within the project:

mise WARN  Failed to resolve tool version list for usage: [~/.config/mise/config.toml] usage@latest: usage@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile

Is this correct that mise cares about versions of tools that are outside of the project and are not defined in the project itself?

[jdx]

This is expected behavior. settings.locked = true is a global setting that applies to all tool resolution, not just project-level tools. When it's enabled, mise requires all tools to be in a lockfile — including ones from your global config.

A couple of options:

1. Pin usage to a specific version in your global config instead of latest (e.g., usage@1.0.0), then run mise install to populate the lockfile.
2. Don't use locked = true globally if you want to use @latest in your global config.

This comment was generated by Claude Code.

[bs-va]

hm, for 2: I'm not using locked = true globally, it's project-only and not set globallly

so the question still stands - is it correct that project-level locked = true cares about tools that are global level?

[carlosjgp]

same here

error

mise WARN  Failed to resolve tool version list for ripgrep: [~/.config/mise/config.toml] ripgrep@15.1.0: ripgrep@15.1.0 is not in the lockfile                              
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for circleci-cli: [~/.config/mise/config.toml] circleci-cli@latest: circleci-cli@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for k9s: [~/.config/mise/config.toml] k9s@latest: k9s@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for kustomize: [~/.config/mise/config.toml] kustomize@5.8.1: kustomize@5.8.1 is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for go: [~/.config/mise/config.toml] go@1.26.1: go@1.26.1 is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for kubectx: [~/.config/mise/config.toml] kubectx@latest: kubectx@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for aws-sso: [~/.config/mise/config.toml] aws-sso@latest: aws-sso@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for tf-summarize: [~/.config/mise/config.toml] tf-summarize@latest: tf-summarize@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for tuist: [~/.config/mise/config.toml] tuist@latest: tuist@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for helm-ct: [~/.config/mise/config.toml] helm-ct@latest: helm-ct@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for helm-docs: [~/.config/mise/config.toml] helm-docs@latest: helm-docs@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for aqua:ankitpokhrel/jira-cli: [~/.config/mise/config.toml] aqua:ankitpokhrel/jira-cli@latest: aqua:ankitpokhrel/jira-cli@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for kubectl: [~/.config/mise/config.toml] kubectl@latest: kubectl@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for node: [~/.config/mise/config.toml] node@latest: node@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for rbac-lookup: [~/.config/mise/config.toml] rbac-lookup@latest: rbac-lookup@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for krew: [~/.config/mise/config.toml] krew@latest: krew@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for sonar-scanner-cli: [~/.config/mise/config.toml] sonar-scanner-cli@latest: sonar-scanner-cli@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for usage: [~/.config/mise/config.toml] usage@latest: usage@latest is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for python: [~/.config/mise/config.toml] python@3.14.3: python@3.14.3 is not in the lockfile
hint: Run `mise install` without --locked to update the lockfile
mise WARN  Failed to resolve tool version list for aqua:alcideio/rbac-tool: [~/.config/mise/config.toml] aqua:alcideio/rbac-tool@latest: aqua:alcideio/rbac-tool@latest is not in the lockfile

global ~/.config/mise/config.toml

[tools]
circleci-cli = "latest"
k9s = "latest"
ripgrep = "15.1.0"
yq = "latest"
kustomize = "5.8.1"
go = "1.26.1"
kubectx = "latest"
tuist = "latest"
tf-summarize = "latest"
aws-sso = "latest"
helm-ct = "latest"
helm-docs = "latest"
node = "latest"
prek = "latest"
python = "3.14.3"
kubectl = "latest"
"aqua:ankitpokhrel/jira-cli" = "latest"
usage = "latest"
rbac-lookup = "latest"
"aqua:alcideio/rbac-tool" = "latest"
krew = "latest"
sonar-scanner-cli = "latest"
gh = "latest"

[settings]
lockfile = false
always_keep_download = true
legacy_version_file = true
idiomatic_version_file_enable_tools = ["python"]
locked = false

project mise.toml

[tools]
jq = "latest"
prek = "latest"
yq = "latest"
gh = "latest"

[settings]
locked = true # change to false to allow updates or installation of tools. Can also use MISE_LOCKED=false mise <cmd>
lockfile = true

[rmorshea-atom-computing]

Pin usage to a specific version in your global config

This suggestion does not seem to help either.

[jdx]

pinning is ai hallucination, sorry about that. I don't think y'all understood what I meant though. I am saying you cannot put lockfile = true into any config file and have it only take affect there as ALL settings are global no matter where they are defined. There is no such thing as project-local settings in mise.

[carlosjgp]

Is there a way to lock the global tools?

[carlosjgp]

Moving my global tools to $HOME allowed me to setup my global configuraiton and lockfile

[rmorshea-atom-computing]

@carlosjgp just discovered that you can run mise lock -g. Should allow you to avoid moving things to $HOME. At least it did for me.

[rmorshea-atom-computing]

It's a bit odd that you can't run mise lock -g in a project directory with locked = true though. Might have assumed the -g flag would avoid the project-specific context.