Some context on the validation so far: Elijah Newren, who wrote git's merge-ort (the default merge strategy), reviewed weave and said language-aware content merging is the right approach, that he's been asked about it enough times to be certain there's demand, and that our fallback-to-line-level strategy for unsupported languages is "a very reasonable way to tackle the problem." Taylor Blau from the Git team said he's "really impressed" and connected us with Elijah. The creator of libgit2 starred the repo. Martin von Zweigbergk (creator of jj) has also been excited about the direction. We are also working with GitButler team to integrate it as a research feature.

The part that's been keeping me up at night: this becomes critical infrastructure for multi-agent coding. When multiple agents write code in parallel (Cursor, Claude Code, Codex all ship this now), they create worktrees for isolation. But when those branches merge back, git's line-level merge breaks on cases where two agents added different functions to the same file. weave resolves these cleanly because it knows they're separate entities. 31/31 vs git's 15/31 on our benchmark.

Weave also ships as an MCP server with 14 tools, so agents can claim entities before editing, check who's touching what, and detect conflicts before they happen.

▲ tveita 28 minutes ago | parent | next [-]

> Elijah Newren, who wrote git's merge-ort (the default merge strategy), reviewed weave and said language-aware content merging is the right approach, that he's been asked about it enough times to be certain there's demand, and that our fallback-to-line-level strategy for unsupported languages is "a very reasonable way to tackle the problem." Taylor Blau from the Git team said he's "really impressed" and connected us with Elijah. The creator of libgit2 starred the repo. Martin von Zweigbergk (creator of jj) has also been excited about the direction.

Are any of these statements public, or is this all private communication?

> We are also working with GitButler team to integrate it as a research feature.

Referring to this discussion, I assume: https://github.com/gitbutlerapp/gitbutler/discussions/12274

	▲	rs545837 25 minutes ago \| parent [-]
		Email conversations with Elijah and Taylor are private. Martin commented on our X post that went viral, and suggested a new benchmark design.

▲ deckar01 13 hours ago | parent | prev | next [-]

Does this actually matter for multi-agent use cases? Surely people that are using swarms of AI agents to write code are just letting them resolve merge conflicts.

▲ vidarh 4 hours ago | parent | next [-]

I'm running agents doing merges right now, and yes and no. They can resolve merges, but it often takes multiple extra rounds. If you can avoid that more often it will definitely save both time and money.

	▲	rs545837 33 minutes ago \| parent [-]
		Thanks for the great explaination again.

▲ rs545837 12 hours ago | parent | prev [-]

So that you don't feel that I am biased about my thing but just giving more context that it's not just me, its actually people saying on twitter how often the merging breaks when you are running production level code and often merging different branches.

https://x.com/agent_wrapper/status/2026937132649247118 https://x.com/omega_memory/status/2028844143867228241 https://x.com/vincentmvdm/status/2027027874134343717

▲ deckar01 12 hours ago | parent [-]

Those users all work for companies that sell AI tools. And the first one literally says they let AI fix merge conflicts. The second one is in a thread advocating for 0 code review (which this can’t guarantee) (and also ew). The third is also saying to just have another bot handle merging.

▲ rs545837 12 hours ago | parent [-]

Thanks a lot for the fair criticism, Appreciate it! You're right that those links aren't the strongest evidence. The real argument isn't "people are complaining on twitter." It's just much simpler when two agents add different functions to the same file, where git creates a conflict that doesn't need to exist. Weave just knows they're separate entities and merges cleanly. Whether you let AI resolve the false conflict or avoid it entirely is a design choice, we think avoiding it is better.

▲ deckar01 12 hours ago | parent [-]

Dear god, it’s bots all the way down.

▲ rs545837 12 hours ago | parent [-]

What do you mean?

▲ deckar01 11 hours ago | parent [-]

It’s your GitHub profile. It looks suspiciously just like the other 10 GitHub users that have been spamming AI generated issues and PRs for the last 2 weeks. They always go quiet eventually. I suspect because they are violating GitHub’s ToS, but maybe they just run out of free tokens.

▲ rs545837 11 hours ago | parent | next [-]

Thanks again for criticising, so tackling each of your comment:

GitHub’s ToS, because you suspect, so I can help you understand them.

> What violates it:

        1. Automated Bulk issues/PRs, that we don't own
        2. Fake Stars or Engagement Farming
        3. Using Bot Accounts.

We own the repo, there's not even a single fake star, I don't even know how to create a bot account lol.

> Scenario when we run out of free tokens.

Open AI and Anthropic have been sponsoring my company with credits, because I am trying to architect new software post agi world, so if I run out I will ask them for more tokens.

▲

deckar01 11 hours ago | parent [-]

And you are opening issues on projects trying to get them to adopt your product. Seems like spam to me. How much are you willing to spend maintaining this project if those free tokens go away?

	▲	rs545837 10 hours ago \| parent [-]
		When you're just a normal guy genuinely trying to build something great and there's nobody who believes in you yet, the only thing you can do is go to projects you admire and ask "would this help you?" Patrick Collison did the same thing early on, literally taking people's laptops to install Stripe.

▲ Palanikannan 11 hours ago | parent | prev [-]

https://github.com/Ataraxy-Labs/weave/pull/11

Dude did you just call me AI generated haha, i've been actively using weave for a gui I've been building for blazingly fast diffs

https://x.com/Palanikannan_M/status/2022190215021126004

So whenever I run into bugs I patched locally in my clone, I try to let the clanker raise a pr upstream, insane how easy things are now.

▲

deckar01 11 hours ago | parent [-]

I think you accidentally switched accounts.

	▲	rs545837 10 hours ago \| parent [-]
		Nope that's other user, he has been working with me on weave, check the PRs that you are calling AI generated.

▲ kubb 9 hours ago | parent | prev | next [-]

Congrats on getting acknowledged by people with credibility.

I also think that this approach has a lot of potential. Keep up the good work sir.

	▲	rs545837 8 hours ago \| parent [-]
		Thanks a lot! Appreciate it.

▲ 6 hours ago | parent | prev [-]

[deleted]