Oak
Shares rank 16 of 26 version control systems by recommenders
Git alternative for agents that mounts branches and avoids full clones, aimed at faster parallel work. Critics doubt the speed gain over git and find the site vague.
Git alternative for agents that mounts branches and avoids full clones, aimed at faster parallel work. Critics doubt the speed gain over git and find the site vague.
26 people gave an opinion
- recommend it
- 12
- criticize it
- 14
- approval share
- 46%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 12 people recommend itNeeds 10 or more, met.
- 0.8 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Mount branches without full clones
“The main site mentions being able to "mount" a branch, vs. cloning a new repo or using git worktrees.”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “Being able to use FSKit/FUSE to make a change to a repo rather than doing a partial/full clone.”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “aligns with a multi-checkout workflow better than git does”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” - Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways”
Built for agent throughput and parallelism
“agents will need to work on tasks much faster and with more parallelism than humans do with Git right now”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “The exciting part to me is that we can already improve on tokens and timing”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “Agentic development is all about throughput, not latency.”
Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways”
What people warn about
Each mark is one comment
Benefit over git unclear
“Why would an agent (without fine tuning or oak-specific context) be faster with oak than it is with git or jj?”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “Looks very interesting, but it's difficult to see the benefit from git right now apart from performance?”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “But how are either of these two things a bottleneck? No case is made for this.”
Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways” - Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways”
- Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways”
AI-generated, marketing-heavy website
“From the obviously slop-generated website, to the wild technical inaccuracies like "Git makes you clone the entire history before you can open a single path"”
Comment from 3 Jul 2026 in “Oak: Git for Agents” “The main issue I see is with the site -- it just seems like a big blob of AI-generated text”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “Oh, it’s “for agents,” you say. Well, I’m sure that makes all the difference.”
Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways” - Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways”
Solves a narrow or invented problem
“Why would I want to like a project which seems to invent problems rather than solve any?”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “the blurb focuses on "saving milliseconds" when that all gets obliterated by the seconds”
Comment from 3 Jul 2026 in “Oak: Git for Agents” “but the use case is limited”
Comment from 23 Jun 2026 in “Git is forever. I'm building Oak anyways”
Other version control systems people recommend
The four most recommended other version control systems, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Git | 814 | 503 | 62% | 13 | 15 yrs42 owners | — |
| Jujutsu (jj) | 335 | 106 | 76% | 13 | 1 yr21 owners | Approved |
| Mercurial | 121 | 43 | 74% | 12 | 19 yrs7 owners | Approved |
| jj (Jujutsu) | 115 | 37 | 76% | 12 | 1 yr7 owners | Approved |
| OakThis page | 12 | 14 | 46% | 2 | — | — |
What people said
29 of the 34 comments that mention it, newest first. Each links to the original comment.
“the blurb focuses on "saving milliseconds" when that all gets obliterated by the seconds”
“From the obviously slop-generated website, to the wild technical inaccuracies like "Git makes you clone the entire history before you can open a single path"”
“Sounds like a good optimization to me.”
“But how are either of these two things a bottleneck? No case is made for this.”
“isn't that too little to justify moving out of git?”
“Mount can be super advantageous in a lot of contexts”
“Oh, it’s “for agents,” you say. Well, I’m sure that makes all the difference.”
“Agentic development is all about throughput, not latency.”
“but the use case is limited”
“Being able to use FSKit/FUSE to make a change to a repo rather than doing a partial/full clone.”
“I'm supposed to use a central technology whose author can't be arsed to write a few paragraphs?”
“Why would an agent (without fine tuning or oak-specific context) be faster with oak than it is with git or jj?”
“I use oak to develop oak and want the experience for agents and humans to be as smooth and wonderful as possible.”
“aligns with a multi-checkout workflow better than git does”
“The exciting part to me is that we can already improve on tokens and timing”
“Now you need to rebuild the world just to add some ergonomics on top of git.”
“Too much going on and hard to parse.”
“Why would I want to like a project which seems to invent problems rather than solve any?”
“the installer asks me to create an account and I don't want to do that yet”
“The main site mentions being able to "mount" a branch, vs. cloning a new repo or using git worktrees.”
“One of the benefits of building from scratch is that this is pretty straightforward.”
“Looks very interesting, but it's difficult to see the benefit from git right now apart from performance?”
“The main issue I see is with the site -- it just seems like a big blob of AI-generated text”
“agents will need to work on tasks much faster and with more parallelism than humans do with Git right now”
“it’s probably some of the worst product marketing I’ve seen”
“seems like an interesting idea”
“the website is much more insightful”
“And yes, no separate LFS system!”
“no concrete comparisons where this tool does a better job than git”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.