Pijul
Hacker ApprovedRanked 9 of 26 version control systems by recommenders
Distributed version control whose patches commute, so changes merge in any order with fewer conflicts. Caveat: immature, with crashes and few basic features.
Distributed version control whose patches commute, so changes merge in any order with fewer conflicts. Caveat: immature, with crashes and few basic features.
46 people gave an opinion
- recommend it
- 32
- criticize it
- 14
- approval share
- 70%
Recommended in 9 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 6 years
Median of the 4 owners who said how long they have had it.
Each square is one year.
Why it carries the badge
- 32 people recommend itNeeds 10 or more, met.
- 2.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 9 of 13 monthsNeeds 4 or more, 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
Works well with parallel AI agents
“I've been using it to build giant things using hundreds of Claude instances in parallel, almost without any conflict, ever.”
Comment from 14 Oct 2026 in “Redesigning source control at Anthropic” “For concurrency reasons Pijul is an excellent git replacement for agents”
Comment from 22 Jun 2026 in “Git is forever. I'm building Oak anyways” “I've been using it with a massive farm of agents to build large things”
Comment from 15 Oct 2026 in “Redesigning source control at Anthropic” - Comment from 10 Apr 2026 in “We've raised $17M to build what comes after Git”
- Comment from 14 Oct 2026 in “Redesigning source control at Anthropic”
Patches commute, fewer merge conflicts
“Once you resolve the conflict of A+B, no future merges or rebases would cause the same conflict again.”
Comment from 23 Mar 2026 in “A Coherent Vision for the Future of Version Control” “eliminates an entire class of merge conflicts which make working in a distributed manner more feasible”
Comment from 1 Dec 2025 in “Migrating Dillo from GitHub” “which Darcs/Pijul don’t require so long as the patches apply since they commute”
Comment from 30 Apr 2026 in “Tangled – We need a federation of forges” - Comment from 23 Mar 2026 in “A Coherent Vision for the Future of Version Control”
- Comment from 15 Jul 2026 in “The Git history command deserves more attention”
- Comment from 22 Mar 2026 in “A Coherent Vision for the Future of Version Control”
Principled patch theory, algebraically sound
“Pijul is a brilliant experiment in Category Theory applied to VCS”
Comment from 12 Apr 2026 in “Pijul a FOSS distributed version control system” “some even more algebraically sound like Darcs and Pijul”
Comment from 10 Apr 2026 in “We've raised $17M to build what comes after Git” “its approach seems fundamentally more right than Git's”
Comment from 12 Apr 2026 in “Pijul a FOSS distributed version control system” - Comment from 28 Apr 2026 in “Ghostty is leaving GitHub”
Darcs successor, capable and performant
“It's darcs' spiritual successor, and quite performant and capable.”
Comment from 18 May 2026 in “Mercurial, 20 years and counting: how are we still alive and kicking? [video]” “I like darcs, so I am rooting for pijul.”
Comment from 11 Apr 2026 in “We've raised $17M to build what comes after Git” “You might like pijul if you like darcs”
Comment from 29 Apr 2026 in “Before GitHub”
What people warn about
Each mark is one comment
Immature and unfinished implementation
“the whole system implementation is so complex my guy is still toiling away on it, unfinished, after half a decade”
Comment from 29 Apr 2026 in “Ghostty is leaving GitHub” “it's still not at a maturity level that I would like”
Comment from 29 Apr 2026 in “Before GitHub” Crashes and network sync bugs
“I tried it a few weeks ago and found it completely unusable. I do not get how they claim to be using it.”
Comment from 11 Apr 2026 in “Pijul a FOSS distributed version control system” “major, seemingly unresolvable crashes for the simplest of operations on Mac and Linux”
Comment from 11 Apr 2026 in “Pijul a FOSS distributed version control system” “it crashed on me a few times on my first day, so I just uninstalled it”
Comment from 10 Apr 2026 in “We've raised $17M to build what comes after Git” - Comment from 23 Mar 2026 in “A Coherent Vision for the Future of Version Control”
Barebones, missing basic features
“Pijul is barebones by design, ready to be scripted, there’s just not much out there.”
Comment from 29 Apr 2026 in “Before GitHub” “Some basic quality of life features were missing, and are still missing.”
Comment from 12 Apr 2026 in “Pijul a FOSS distributed version control system” Weak git compatibility and adoption
“I was kind of hoping Jujitsu or Pijul would take a stab at these major Git deficiencies but unfortunately it seems like they are content to do them as badly as Git does.”
Comment from 17 Jun 2026 in “Epic Games announces Lore version control system” “Just stop using rebase is much easier to socialize than let's all move to Pijul.”
Comment from 12 Apr 2026 in “Pijul a FOSS distributed version control system”
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 |
| PijulThis page | 32 | 14 | 70% | 9 | 6 yrs4 owners | Approved |
What people said
40 of the 61 comments that mention it, newest first. Each links to the original comment.
“I've been using it with a massive farm of agents to build large things”
“I've been using it to build giant things using hundreds of Claude instances in parallel, almost without any conflict, ever.”
“it works really well for agent collaboration”
“patch theory guaranteeing you can "apply" commits in any order”
“pijul at least looks cool even if I don't know if it scales well”
“Pijul natively handles monorepos btw, that's the whole point.”
“For concurrency reasons Pijul is an excellent git replacement for agents”
“I was kind of hoping Jujitsu or Pijul would take a stab at these major Git deficiencies but unfortunately it seems like they are content to do them as badly as Git does.”
“It's darcs' spiritual successor, and quite performant and capable.”
“which Darcs/Pijul don’t require so long as the patches apply since they commute”
“it's still not at a maturity level that I would like”
“Pijul is barebones by design, ready to be scripted, there’s just not much out there.”
“the whole system implementation is so complex my guy is still toiling away on it, unfinished, after half a decade”
“You might like pijul if you like darcs”
“Pijul & Darcs still have better fundamentals.”
“first class support for "how do I combine these" which git mostly discards as unimportant”
“its approach seems fundamentally more right than Git's”
“Pijul is a brilliant experiment in Category Theory applied to VCS”
“Just stop using rebase is much easier to socialize than let's all move to Pijul.”
“Some basic quality of life features were missing, and are still missing.”
“diffs can't show context. They show lines removed and added, but can't show the previous and following line”
“I tried it a few weeks ago and found it completely unusable. I do not get how they claim to be using it.”
“the network effect of git at this point is too strong”
“major, seemingly unresolvable crashes for the simplest of operations on Mac and Linux”
“I like darcs, so I am rooting for pijul.”
“some even more algebraically sound like Darcs and Pijul”
“it seems really nice for working with an agent”
“These are all version control systems that are better than git in various ways.”
“it crashed on me a few times on my first day, so I just uninstalled it”
“everything sound awesome : quite no more merge conflict and patches order free”
“encounter a no-workaround-possible bug in the network sync”
“Once you resolve the conflict of A+B, no future merges or rebases would cause the same conflict again.”
“hundreds - perhaps thousands - of hours of real expert developer's toil put in it”
“changes are patches and are commutative”
“because Pijul uses Pijul for development, not Git and GitHub”
“it has hundreds - perhaps thousands - of hours of real expert developer's toil put in it”
“exploring both as alternatives to git and alternative's to git's ideas/dominance is still a handy idea”
“I liked pijul a bunch too but lack of compat with git meant I can't use it for work”
“Much more principled (and hence less of a foot-gun) way of handling conflicts is making them first class objects in the repository”
“eliminates an entire class of merge conflicts which make working in a distributed manner more feasible”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.