Oak: open-source VCS designed for AI coding agents
1 min read
Originally from oak.space
View source
My notes
Summary
Oak is a new open-source VCS (Rust, Apache-2.0, public beta v0.100.0) designed for AI coding agents rather than humans. It replaces git’s per-commit-message model with branch-per-session as the unit of work, plus branch descriptions and content-addressed lazy mounts that hydrate on demand, letting an agent open and edit any repo in seconds.
Key Insight
- The pitch is substrate for agents, not “git but faster.” Speed (vs git) is a side effect of content-addressing + lazy hydration, not the goal.
- Branch-per-session is the unit of work. Each agent run = its own branch. No more squashing or per-commit message theatre.
- Two crates:
oakvcs-core(reusable library, default-features off = no SQLite/git deps) andoakvcs-cli(theoakbinary). Embeddable in other tooling. - Bring-your-own-agent: explicitly designed to be driven by Claude Code, Codex, Cursor, etc. Not tied to a single vendor.
- Install on macOS Apple Silicon / Linux x86_64 via
curl -fsSL oak.space/install | sh. Windows needs the Projected File System (ProjFS) feature enabled foroak mount; everything else (clone/push/pull/commit) works without it. - TLS via rustls + ring, no C/NASM toolchain needed for
cargo install oakvcs-cli. Friendlier supply chain than most Rust crates touching openssl. - Self-aware footnote: the repo itself was written almost entirely by AI with human oversight, eating their own dog food.