Show HN: Moo, Git versions code, moo versions machines

I'm Evan, CTO of Ito (ito.ai). We do code review that actually runs your code. When we're developing locally, we run lots of coding agents in parallel against the same repo, and we kept hitting the same wall: git worktrees isolate files, but the database, ports, and services all collide.

Moo is a brand new internal tool we use to moove faster and thought we'd share it.

Every branch or agent attempt gets its own isolated Linux machine, and the machine's state is versioned with your repo. Moo save snapshots the runtime tagged with the current commit. Check out an old SHA, run moo new, and you boot the exact runtime that existed there.

It's microVMs with copy-on-write (CoW) disks under the hood. Forking a 20 GB environment is <500ms.

Right now it's only macOS Apple Silicon only due to depending on libkrun and APFS clonefile.