Add subcommand for mise tasks to include in the global config.toml an external tasks.toml

[gturi]

It would be nice to have a mise tasks command to include external tasks.toml configuration in the global [task_config] section.

Purpose: pulling global tasks from a git repository and automate their setup in the global configuration file.

Example:

# setup.sh
mise tasks include /path/to/tasks.toml
mise tasks include /another/path/to/tasks.toml
mise tasks include /path/to/file/tasks
# mise detects path already included and does not add it multiple times
mise tasks include /path/to/tasks.toml

# ~/.config/mise/config.toml
[task_config]
includes = [
  "/path/to/tasks.toml",
  "/another/path/to/tasks.toml",
  "/path/to/file/tasks"
]

[gturi]

This command could also check or automatically detect broken includes (i.e. the pointed path not being present anymore) and provide a way to delete them.

[JamBalaya56562]

mise tasks include still does not exist — on 2026.8.6 the subcommands are add, deps, edit, graph, info, ls, run, validate. Here is where each of the three things you asked for stands, all measured on that version.

Adding a path idempotently

Unimplemented. The nearest primitive is mise config set, and it does the opposite of what you asked for:

$ mise config set task_config.includes '/a,/b' --type list
$ mise config set task_config.includes '/c' --type list

# mise.toml
[task_config]
includes = ["/c"]

It replaces the list rather than appending to it, so a setup.sh calling it once per repository ends up with only the last one. (--type list splits on commas, so the whole list has to go in a single call.)

One thing worth knowing before automating this

task_config.includes replaces the default file-task directories for that config scope rather than adding to them — docs. The defaults are mise-tasks, .mise-tasks, .mise/tasks, .config/mise/tasks and mise/tasks.

So the moment a script writes an includes list into the global config, mise stops looking in those five directories unless the script lists them too. That is the part I would want to know before wiring this into a bootstrap script — and it also shapes the answer to your next ask.

Detecting a broken include

Silent today, and deliberately so. Measured with includes = ["does-not-exist.toml"]:

$ mise tasks ls
hello

$ mise tasks validate
✓ All 1 task(s) validated successfully

Nothing at --verbose either.

I proposed making it warn (#11883). jdx declined it, and the reasoning is worth repeating because it answers your ask rather than deferring it: include entries are search candidates, and a missing candidate can be perfectly deliberate — the documentation recommends listing all five default directories when you add a custom one, and most of those are normally absent, so warning would make the documented configuration noisy. It matches how other config and env-file search paths behave: they quietly skip what is not there.

So this is not an oversight waiting for a patch; it is the intended behaviour.

Deleting a broken include

Unimplemented, and it follows from the point above — if a missing entry is a legitimate state rather than an error, there is no "broken" for such a command to clean up.

What that leaves

The idempotent-append idea is the only one of the three not settled by a design decision, and it is unclaimed. Until then the shape that works is to build the whole list yourself — the defaults you want, plus your own paths — and write it in one mise config set … --type list call.