conf.d fragments

Every .toml file in .config/mise/conf.d/ is loaded by mise in alphabetical order, and applies to every directory in the workspace. The numeric prefix is the load order.

The mechanism is explained in the conf.d merge model; this page is the inventory.

The shipped fragments

00-settings.toml

Global behaviour. Loads first so everything after inherits it.

auto_install = false
jobs = 4

Setting	Effect
auto_install = false	Entering a directory never installs anything. See explicit installs.
jobs	Parallel install workers

10-core-tools.toml

Interpreters and compilers: python, node, go, rust, java, dart, flutter.

20-cli-tools.toml

The toolbelt: eza, bat, ripgrep, fd, jq, zoxide, delta, btm.

These are not required by any project — they are the shell you actually want to work in, made portable along with everything else.

30-package-managers.toml

bun, deno, pnpm, uv, zig, cmake, ninja.

Writing your own

.config/mise/conf.d/40-elixir.toml

[tools]
erlang = "latest"
elixir = "latest"

Reserved ranges:

Range	Category
00-	settings
10-	interpreters and compilers
20-	CLI toolbelt
30-	package managers and build tools
40-+	yours

One tool, one fragment

If two fragments declare the same tool, the alphabetically later file wins — silently. Keep each tool in exactly one place.

Nested mise.toml files

conf.d/ is for things you want everywhere. For anything scoped to one language area, use that area’s config instead:

Workspace/Go/mise.toml

[env]
CGO_ENABLED = "0"

[tasks.test]
run = "go test ./..."

A nested config inherits its parents’ tools, environment and tasks, and overrides only the keys it names.

Applying changes

polyforge install
polyforge status

There is no watch mode and no reload — that is the explicit installs decision at work.