Weave merge tool
Ranked 2 of 13 diff tools by recommenders
An entity-level merge driver that plugs into git and avoids many false conflicts by understanding code structure. Critics report silent corruption and merges that fail on some code.
An entity-level merge driver that plugs into git and avoids many false conflicts by understanding code structure. Critics report silent corruption and merges that fail on some code.
31 people gave an opinion
- recommend it
- 20
- criticize it
- 11
- approval share
- 65%
Recommended in 6 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 20 people recommend itNeeds 10 or more, met.
- 1.8 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 6 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
Merges at entity level, avoiding false conflicts
“For the merge use case (weave - https://ataraxy-labs.github.io/weave/ ), that level of understanding is enough to resolve 100% of false conflicts on our benchmarks.”
Comment from 9 Mar 2026 in “Sem – Semantic version control. Entity-level diffs on top of Git” “Weave treats entities as unordered sets, so two agents adding different functions at the end of a file just get unioned.”
Comment from 16 Feb 2026 on Hacker News “The entity-level approach is a meaningful step up from line-based merging.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” - Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
- Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
- Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
- Comment from 30 Apr 2026 in “Vera: a programming language designed for machines to write”
- Comment from 11 Feb 2026 on Hacker News
Helps LLM and agent workflows
“The MCP server angle is the more interesting long-term bet here because it moves conflict avoidance earlier in the workflow rather than cleaning up damage after the merge.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” “I was interested in the general merge approach, and that it works with LLMs and agents fine”
Comment from 14 Jun 2026 in “Weave: Merging based on language structure and not lines” “it improves the agents performance, especially if you are a power user.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” - Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
- Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
Plugs into git's merge driver
“Your git doesn't change at all. Weave plugs in through git's merge driver interface”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” “takes it further and does git merges at entity level”
Comment from 30 Apr 2026 in “Vera: a programming language designed for machines to write” “Weave replaces git's merge with entity-level merge.”
Comment from 11 Feb 2026 on Hacker News Adds language support over time
“we are supporting bash tree sitter grammar now with weave”
Comment from 6 Mar 2026 in “Weave – A language aware merge algorithm based on entities” “Very cool, would love to see Ruby support added.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” “Nice, thanks for the Ruby support!”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities”
What people warn about
Each mark is one comment
Silently corrupts or drops code
“Silent corruption that wouldn't go away no matter how many issues I filed. Unacceptable. Had to disable it.”
Comment from 14 Jun 2026 in “Weave: Merging based on language structure and not lines” “I have noticed some rather concerning merge "resolutions".”
Comment from 20 Mar 2026 in “Kin: Semantic version control that tracks code as entities, not files” “noticed that code was disappearing. I no longer use it.”
Comment from 14 Jun 2026 in “Weave: Merging based on language structure and not lines” Misses some conflicts and refactors
“yeah there are some failure cases but I love to receive any feedback that you think can improve it”
Comment from 14 Jun 2026 in “Weave: Merging based on language structure and not lines” “I tried this with the kind of merge conflict I'd expect it to solve automatically, and it didn't.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” “This will not work for refactors. In fact, any other change will break the hash.”
Comment from 4 Mar 2026 in “Weave – A language aware merge algorithm based on entities” Little gain over alternatives like mergiraf
“apart from TypeScript, I haven't found any cases where it actually outperforms mergiraf”
Comment from 14 Jun 2026 in “Weave: Merging based on language structure and not lines” “I haven't really felt they've earned their keep.”
Comment from 23 Sep 2026 in “Show HN: Foremerge – Catch intent conflicts between parallel coding agents”
Other diff tools people recommend
The four most recommended other diff tools, 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 |
|---|---|---|---|---|---|---|
| difftastic | 23 | 1 | 96% | 10 | — | Approved |
| Weave merge toolThis page | 20 | 11 | 65% | 6 | — | — |
| Mergiraf | 19 | 4 | 83% | 5 | 6 mo3 owners | Approved |
| sem | 19 | 7 | 73% | 5 | — | Approved |
| Meld | 12 | 2 | 86% | 5 | — | Approved |
What people said
40 of the 49 comments that mention it, newest first. Each links to the original comment.
“I haven't really felt they've earned their keep.”
“deterministic interleaving explorer, roughly what Loom is for Java”
“I find the organization level view and pivots useful and aligned with intuitive expectations.”
“We take this stuff super seriously”
“noticed that code was disappearing. I no longer use it.”
“I was interested in the general merge approach, and that it works with LLMs and agents fine”
“so much text with little context. Looks like AI fluff”
“yeah there are some failure cases but I love to receive any feedback that you think can improve it”
“Silent corruption that wouldn't go away no matter how many issues I filed. Unacceptable. Had to disable it.”
“I think this is a great idea, and I've wondered about something like this before.”
“apart from TypeScript, I haven't found any cases where it actually outperforms mergiraf”
“takes it further and does git merges at entity level”
“I have noticed some rather concerning merge "resolutions".”
“For the merge use case (weave - https://ataraxy-labs.github.io/weave/ ), that level of understanding is enough to resolve 100% of false conflicts on our benchmarks.”
“we are supporting bash tree sitter grammar now with weave”
“that's exactly why weave ships an MCP server alongside the merge driver”
“The MCP server angle is the more interesting long-term bet here because it moves conflict avoidance earlier in the workflow rather than cleaning up damage after the merge.”
“that's pretty cool, thank you”
“weave runs post-merge validation for exactly this”
“it improves the agents performance, especially if you are a power user.”
“Parsing three file versions at merge time is fine”
“used weave in merge conflicts there which helped him”
“Nice, thanks for the Ruby support!”
“i've been actively using weave for a gui I've been building for blazingly fast diffs”
“entity-level context cuts tokens that much validates the whole thesis”
“This will not work for refactors. In fact, any other change will break the hash.”
“I tried this with the kind of merge conflict I'd expect it to solve automatically, and it didn't.”
“was able to auto resolve so much”
“Awesome, I've been wanting this for a long time!”
“Weave just knows they're separate entities and merges cleanly.”
“Your git doesn't change at all. Weave plugs in through git's merge driver interface”
“The entity-level approach is a meaningful step up from line-based merging.”
“people saying on twitter how often the merging breaks when you are running production level code”
“Simpler, faster, and conflicts are readable”
“tracking entities is more semantically rich than lines”
“weave resolves these cleanly because it knows they're separate entities”
“Very cool, would love to see Ruby support added.”
“this sounds like it would be really valuable to me”
“Weave treats entities as unordered sets, so two agents adding different functions at the end of a file just get unioned.”
“Weave replaces git's merge with entity-level merge.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.