weave

Entity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge.

Not yet testedsource: GitHubhomepageRustApache-2.0commit 148c09f6f5d2

Rust, Apache-2.0 licensed. The project labels itself: ai agents, code intelligence, coding agents, conflict resolution, developer tools, git merge, llm tools and mcp.

weave has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
1,316
forks
46
open issues
2
watchers
4
size
99 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

ai-agentscode-intelligencecoding-agentsconflict-resolutiondeveloper-toolsgit-mergellm-toolsmcpmerge-drivertree-sitter

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/weave.svg)](https://argusic.com/subject/weave)

Questions

Does weave run?
weave has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test weave?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for weave?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion