Moo, Git versions code, moo versions machines

Name: Moo, Git versions code, moo versions machines
Availability: InStock
Author: dumbfoundded

by dumbfoundded·Jul 8, 2026·9 points·0 comments

Visit Project View on HN

AI Analysis

●●●BangerBig BrainWizardrySolve My Problem

Git versions files, moo versions machines—CoW disk forking in under 500ms.

Strengths

•Copy-on-write disks fork 20GB environments in under 500ms with megabyte overhead.
•Machine state versioned with git—git bisect boots exact runtime at every commit.
•Solves real pain: parallel agents colliding on ports, databases, and services.

Weaknesses

•Apple Silicon only currently—Linux hosts planned but not shipped.
•Alpha status with snapshot format potentially changing between releases.

Post Description

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.