A declared toolchain
Python, Go, Rust, Node, Java, Dart, Flutter, C++ and a CLI toolbelt, declared in modular TOML fragments that merge automatically.
PolyForge
PolyForge is a portable, polyglot development workspace driven entirely by mise. Clone it, run one command, and every language toolchain is a single explicit install away — behind three commands that behave identically on Windows, macOS, Linux and WSL.
It is not a package manager and not a dotfiles repo. It is the thin layer that makes one machine’s development environment reproducible on the next one.
What you get
Section titled “What you get”Three commands
polyforge for the workspace, learn for structured practice, forge for
your template library. Registered together, identical on every platform.
A clean tooling repo
Your actual code never enters this repository. A committed registry maps names to repos and restores them on demand.
No surprise downloads
auto_install = false. Entering a directory never pulls tools in the
background — you install when you decide to.
Start here
Section titled “Start here”InstallationPrerequisites and the one-shot initializer, on every platform.
First runWhat activation actually does, step by step, and how to verify it.
Your first projectScaffold, work, publish, and restore it on another machine.
Understand the design
Section titled “Understand the design”The architecture is the interesting part. If you only read one section, read these.
The conf.d merge modelWhy the toolchain is split into fragments, and how mise cascades them up the tree.
Content separationWhy your code lives in its own repos and how the registry brings it back.