Mitts Build
Rust-first build tooling with a shared content-addressed artifact cache.
Status from GitHub and crates.io as of 2026-11-06.
The problem
Separate checkouts can repeat compilation work. Mitts reads Cargo manifests and lockfiles, plans compilation actions and invokes rustc, using a machine-wide artifact store to reuse eligible outputs.
Example uses
01. Separate worktrees
Evaluate artifact reuse across native builds whose tracked inputs match.
02. Inspect a build plan
Use mitts explain to inspect compilation units and their cache eligibility.
03. Native Rust workloads
Try supported Cargo workspace builds while retaining Cargo for unsupported cases.
Where it fits
Mitts handles build planning and execution. prod-code provides remote code intelligence and command execution; these are different responsibilities.
Get started
git clone https://github.com/alex09x/mitts
cd mitts
cargo install --path .Pre-release source is available on GitHub. Follow the repository instructions and compatibility limits before using it for a project.
Authoritative installation steps, architecture diagrams, and full configuration references are maintained in the repository:
Read the Mitts Build README on GitHub →
Limitations
- Pre-release software; the current GitHub snapshot has no published release.
- Linux and macOS, with native host targets; Windows and cross-compilation are not supported.
- The artifact cache is local to one machine; remote or team caching is not available.
- Not every compilation unit is cacheable, and reuse across checkouts has additional input restrictions.
- Build scripts are not sandboxed; undeclared inputs can invalidate cache assumptions.