weave

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

Runssource: 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 runs. An Argusic agent installed it in 14 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

weave 0.5.4 builds from source, all 505 tests pass, weave and weave-driver binaries run correctly and perform entity-level semantic merges on Python and JavaScript files with clean auto-merges for independent changes and structured conflict markers for real collisions.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
1,364
forks
49
open issues
6
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.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
14 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test: 505 passed, 0 failed across 22 test suites; weave merge: two branches adding different functions auto-merged cleanly; weave-driver conflicting entity merge produced conflict markers with exit 1
Model tokens used
44,361
Exact commit tested
148c09f6f5d2
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Weave** is an entity-level semantic merge engine for Git. It uses tree-sitter to parse code into …
**What was done:**
- Installed Rust toolchain via rustup (rustc 1.100.0, cargo 1.100.0)
- Built all 6 workspace crates from source in release mode
- Installed `weave` (CLI) and `weave-driver` (git merge driver) binaries
- Ran the full test suite: **505 tests, 0 failures** across `weave-core` (368 tests), `weave-cli` (…
- Verified `weave --version` → `weave 0.5.4`
- Verified `weave-driver --help` prints full usage
- Tested `weave setup` configures a git repo with merge driver and `.gitattributes`
- Tested a real git merge: independent function additions on two Python branches → auto-merged clea…
- Tested the driver directly with conflicting entity edits → conflict markers with `refused_by:` en…
**No errors encountered.** No third-party API keys needed. No mocks required. Everything worked fro…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 14 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.

Of the 124 ai-agents projects Argusic has installed and timed, weave was the 94th fastest to reach a running state, and 96 of 124 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • Following its own README: the documented path worked with nothing to fix.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.05
Argusic Runner1/3Runs100.000.05

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?
Yes. weave runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test weave?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 148c09f6f5d2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test weave?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does weave take to install?
14 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does weave need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing weave?
Nothing did, in the recorded run: zero errors between clone and running.
How does weave compare with the alternatives?
Of the 124 ai-agents projects Argusic has installed and timed, weave was the 94th fastest to reach a running state, and 96 of 124 reached one at all.
Where is the evidence for weave?
All 2 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