The archive · Developer & Business Tools · Product decision · 2026
Oak VCS bets AI coding agents need a Git alternative built for sessions, not commits
Bootstrapped Oak VCS (oak.space) ships a Git alternative shaped for AI agents — lazy mounts, branch-per-session work — and scores 216 points on Show HN
Oak VCS
What the business is
Open-source, content-addressed version control system (Rust workspace: oakvcs-core plus the oak CLI) with a hosted platform at oak.space — agents clone, mount, branch and merge repos with native CI and a merge gate, marketed as "version control at the speed of agents"
Starting capital：Bootstrapped — the founder says Oak ran "fully bootstrapped on Oak with no Git backup" for months before launch; no external funding disclosed
How it started
Zach Geier (zdgeier) built Oak in Rust — the README says the repo "was written almost entirely using AI with human oversight" — around a conviction that agents work in parallel sessions and should not inherit Git's commit rituals. He dogfooded it for months, running Oak's own development entirely on Oak with no Git backup, then posted Show HN on 2026-06-22 pitching version control that does not waste "you or your agents' time".
What happened
The thread drew 216 points and 189 comments, mostly comparing Oak to Jujutsu, Fossil, Epic's Lore and Zed's DeltaDB; several shallow dismissals were flagged. Geier answered that every file is chunked so Oak needs no separate LFS, and promised monorepo features. Six weeks later the CLI had moved from v0.99 to v0.102, Windows and native CI shipped (oakspace's own build and deploy left GitHub Actions on 2026-07-06), more than 100 feedback items had been filed from the terminal — most by agents mid-task — and a merge gate plus repo-declared path permissions had landed.
No ending yet — it is still running.
Background
Oak VCS (oak.space) is a bootstrapped version-control startup betting that AI coding agents — not humans — are becoming the primary users of version control. Its open-source Rust core (oakvcs-core plus the oak CLI) is content-addressed and designed around how agents work: branch-per-session as the unit of work, branch descriptions instead of per-commit messages, and lazy mounts that give an agent a working tree without cloning a full repository.
Founder Zach Geier built the system with heavy AI assistance and dogfooded it for months — Oak's own repos ran fully bootstrapped on Oak with no Git backup — before posting Show HN on 2026-06-22. The pitch: agents locally and in the cloud should not download a whole repo to make one change, and Git's human-oriented workflow wastes agent time.
The thread drew 216 points and 189 comments, much of it comparing Oak with Jujutsu, Fossil, Epic's Lore and Zed's DeltaDB; several shallow dismissals were flagged by moderators. Geier engaged directly, explaining that chunked storage removes the need for a separate LFS and promising monorepo features.
Six weeks after launch the CLI had moved from v0.99 to v0.102 with Windows and native CI shipping, and more than 100 feedback items had been filed from the terminal, mostly by agents mid-task. As of September 2026 Oak is still a public beta, still bootstrapped, with no revenue or funding disclosed.
What has to be true
- Git encodes a human workflow — index, commit messages, code review — that agents burn context on, so Oak bet a redesign around sessions and mounts beats tooling on top of Git
- Full clones are the bottleneck: content-addressed lazy mounts let local and cloud agents start editing any repo in seconds, and parallel agents stop fighting worktrees
- Dogfooding made the claim testable: running the company's own repos on Oak with no Git backup meant the product found its own bugs by shipping itself
- A merge gate plus repo-declared path permissions closes the loop for agent-driven changes, and a bundled SKILL.md keeps agents from reaching for git status
- The 189-comment reception shows the wedge is contested — Jujutsu, Fossil, Epic Lore and Zed DeltaDB are all chasing the same agent-native workflow
What can be applied
When the user of a tool changes — agents, not humans, now write most commits — the substrate is the product: redesign the workflow instead of teaching the new user Git's rituals
Aftermath
As of 2026-09-05 Oak remains a bootstrapped public beta (v0.102.1) with installers for macOS, Linux and Windows. The hosted platform runs native CI — since 2026-07-06 it ships oakspace itself — plus a merge gate, repo-declared path permissions and an agent-driven feedback loop; issues and comments features are still missing. The founder's roadmap points to checkout-free branch review, a branch-identity redesign and a "software factory" orchestration layer behind a feature flag. No revenue, user counts or funding have been disclosed.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card