Show HN: Oak – Git alternative designed for agents

Original Article ↗ Hacker News Discussion ↗

What Oak Is and Core Ideas

  • New version control system positioned as Git alternative, especially for AI agents.
  • Key features: virtual/network mounts via FUSE/FSKit, chunked storage for all files (no separate LFS), simplified branching, and integrated hosting.
  • Emphasis on fast, parallel “branch per task” workflows and monorepo-friendly features (e.g., potential to open‑source subtrees while keeping rest private).

Performance, Mounts, and Agent Workflows

  • Proponents: mounts let agents work without full clones, which helps for large repos, frequent tasks, and many parallel workspaces.
  • Claimed benefits: much faster operations than Git, fewer VCS-related tokens via structured/JSON outputs, and quicker spin‑up for cloud agents.
  • Skeptics: for most agent workflows, VCS latency and token use are a tiny fraction of overall LLM cost and wall time; human decision-making is the real bottleneck.

“For Agents” Positioning

  • Supporters: Git’s worktrees and clone-heavy workflows don’t map cleanly to high‑parallelism agent scenarios; specialized defaults and mounts may matter at scale.
  • Critics: models already know Git deeply; any new VCS starts with a learning tax and requires skills/docs. Many argue Git + small wrappers, hooks, or harness tricks are sufficient.
  • Unclear: whether Oak’s gains remain meaningful once Git is carefully wrapped and optimized in the agent harness.

Git’s Pain Points and Alternative VCSes

  • Common Git issues raised: large binaries and LFS, submodules, monorepo scaling, awkward worktrees, history rewriting, and usability.
  • Several mention other systems (Mercurial, Fossil, Jujutsu, Pijul, Sapling, Perforce, Epic’s Lore, Google Piper/CitC, Meta’s EdenFS) as prior art for better UX or virtualized checkouts.
  • Some suggest Oak could have been a Git backend/wrapper; author prefers a clean-slate design, but future Git interoperability is floated.

UX, Messaging, and Product Fit

  • Multiple comments: homepage/blog are confusing, overly self-promotional, and light on concrete comparisons and data model explanation.
  • Strong advice to lead with: what Oak does better than Git, why agents specifically benefit, and real benchmarks.
  • Overall sentiment: idea is interesting; adoption will be very hard without clearer value beyond performance and mounts.