mise trust

• Usage: mise trust [FLAGS] [CONFIG_FILE]
• Effect: modifies state
• Source code: src/cli/trust.rs

Marks a config file as trusted

This means mise is allowed to parse the file when it needs to read config that may execute code or affect the environment. Without trust, mise may prompt, skip the config in some discovery paths, or fail with an untrusted-config error when it cannot prompt.

In normal mode, commands that execute project-defined behavior (mise run, naked task invocations such as mise <TASK>, mise install, mise exec, and mise watch) automatically trust their active config. Paranoid mode requires explicit, content-bound trust for every non-global config.

In normal mode, safe config files do not require trust: files that only contain min_version, [tools] entries with plain version strings (or arrays of them), and [tasks] without templates or tool options.

Trust is shared across git worktrees: a config file inside a linked worktree is trusted when the equivalent path in the repository's main checkout has been trusted. Paranoid mode disables this sharing since worktrees can check out branches with different config contents.

Arguments

• [CONFIG_FILE] — The config file whose trust status to change

Flags

• -a --all — Trust all config files in the current directory, its parents, and its subdirectories

  Subdirectories are walked respecting .gitignore, skipping hidden directories and common build/dependency directories (node_modules, vendor, target, dist, build).

• --ignore — Do not trust this config and ignore it in the future

• --show — Show the trusted status of config files from the current directory and its parents. Does not trust or untrust any files.

• --untrust — Remove explicit trust for this config

• -h --help — Print help

Examples:

# trusts ~/some_dir/mise.toml
$ mise trust ~/some_dir/mise.toml

# trusts mise.toml in the current or parent directory
$ mise trust