Git was built for humans typing commit messages. AI coding agents don’t work that way — they branch constantly, snapshot mid-task, and touch huge repos they never fully read. Oak, shown on Hacker News this week, is a version control system rebuilt for how agents actually operate.
## What’s different
Oak mounts a repo without a full clone — files stream in on first read, so an agent can work against a massive codebase instantly instead of waiting on a download. It branches per task, snapshots up to 95% faster than git, and drops the commit-message tax entirely: you describe a branch once, at the end, and checkpoints carry no message. For an agent that commits dozens of times per task, that removes a real source of latency and wasted tokens.
## Why it matters for agents
Under the hood, Oak chunks and dedupes natively. Change one tensor in a large file and only that chunk travels, instead of re-storing the whole thing — which matters when agents iterate on models and binaries, not just text. It’s a bet that as agents write most of the code, the tooling beneath them gets rebuilt around machine workflows rather than human ones.

Leave a comment