# Install weave with Homebrew, Nix

Entity-level semantic merge driver for Git using tree-sitter. Version 0.3.6 via Homebrew; verified 2026-06-19. Also installable with nix: nix profile install nixpkgs#weave.

## Install

```sh
sudo av install brew:weave
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install weave
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#weave
```

  Evidence: nixpkgs package indexes: pkgs/by-name/we/weave/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:weave
- **Package manager:** Homebrew
- **Version:** 0.3.6
- **Source summary:** Entity-level semantic merge driver for Git using tree-sitter
- **Homepage:** <https://ataraxy-labs.github.io/weave/>
- **Repository:** <https://github.com/Ataraxy-Labs/weave>
- **Last updated:** 2026-06-19T14:33:18+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- weave-driver (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.3.6
## Project history and usage

weave is an entity-level semantic merge driver for Git from Ataraxy Labs. It replaces Git's normal line-oriented merge driver for supported file types, parses code with tree-sitter, and tries to merge functions, classes, methods, JSON keys, and other entities rather than raw line ranges.

The tool is framed around a newer collaboration problem: multiple humans or AI coding agents editing the same repository at the same time. Its promise is to reduce false conflicts when two branches change different semantic entities in the same file.

### Project history

weave is part of Ataraxy Labs' agent-native development stack alongside related semantic version-control and inspection tools. Public packaging and release metadata point to a young Rust project: the weave-driver crate was created on March 14, 2026, and its public Git tags reached the 0.3 series by 2026.

The project site and README position weave as a Git-compatible merge-driver protocol implementation. Users can install it with Homebrew, run weave setup in a repository, and then continue using ordinary git merge while Git invokes weave-driver for supported paths.

weave's public documentation compares it with both Git's line-based merge and Mergiraf. Its benchmark page claims 31 of 31 clean merges across seven languages, plus real-world replay tests on repositories such as git, Flask, CPython, Go, and TypeScript.

### Adoption history

Because weave is new, its adoption history is still early and mostly developer-tool community oriented. The project site reports 1,500-plus downloads and highlights discussion around multi-agent workflows, Git false conflicts, and semantic conflict markers.

The strongest evidence of adoption so far is packaging and discoverability rather than long institutional use: a Homebrew formula, crates.io publication for weave-driver, GitHub releases/tags, and docs that target direct integration with Git and Jujutsu.

### How it is used

The normal setup path is to install weave, run weave setup, and let it write Git merge-driver configuration and attributes for supported file types. A local setup can use .git/info/attributes; a global setup can write rules to ~/.gitconfig and the user's global attributes file.

During a merge, weave parses base, ours, and theirs into semantic entities. Independent entity changes are auto-resolved, incompatible edits to the same entity become contextual conflicts, and unsupported file types fall back to standard line-level merge.

### Why package nerds care

weave is significant because it packages structural merging as a drop-in Git merge driver rather than a separate VCS. That keeps the operational surface small while attacking a real pain point in parallel coding work: line conflicts that are not semantic conflicts.

Its nerd appeal is also in the comparison set. Git's default merge, Mergiraf's AST-aware approach, tree-sitter language grammars, Jujutsu merge tools, and MCP-based agent orchestration all meet in one package.

### Timeline

- 2026-03-14: crates.io records the first weave-driver crate publication.
- 2026-04 to 2026-05: weave-driver receives multiple 0.2 and 0.3 series crate releases.
- 2026: The public Git repository carries tags through the 0.3 series and the project docs advertise Homebrew installation, Git setup, Jujutsu setup, and MCP tools.

### Related projects

- weave is related to Git merge drivers, Jujutsu merge tools, Mergiraf, tree-sitter, Ataraxy Labs sem, Ataraxy Labs inspect, and MCP-based coding-agent workflows.

### Sources

- <https://ataraxy-labs.com/weave>
- <https://ataraxy-labs.github.io/weave/>
- <https://crates.io/crates/weave-driver>
- <https://github.com/Ataraxy-Labs/weave>
- <https://raw.githubusercontent.com/Ataraxy-Labs/weave/main/README.md>


## Security Notes

No matching local secret-handling manifest was found for weave. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .gitattributes, .git/info/attributes, ~/.gitconfig, ~/.config/git/attributes
## Other Package-Manager Records

- Nix - weave: normalized package name match | nixpkgs package indexes: pkgs/by-name/we/weave/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/weave.yml](https://github.com/mxcl/pkgdb/blob/main/combined/weave.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph