Ataraxy-Labs/weave

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

What it solves

Git's line-based merge often creates "false conflicts" when two developers (or AI agents) add independent code—such as different functions—to the same file. Weave replaces this with entity-level merging, ensuring that changes to different functions, classes, or JSON keys are auto-resolved without requiring manual human intervention.

How it works

Weave uses tree-sitter to parse code into semantic entities (functions, classes, etc.) across three versions of a file: the base, the current branch (ours), and the incoming branch (theirs). It matches these entities by identity (name, type, and scope) and merges them individually. If two branches modify different entities, they are auto-resolved; if they modify the same entity, Weave attempts an intra-entity merge or flags a semantic conflict with detailed context.

Who it’s for

Software developers and AI agent frameworks that frequently perform concurrent edits on the same codebase and want to reduce merge conflict overhead.

Highlights

  • Entity-level granularity: Merges functions and classes rather than lines, resolving conflicts that Git cannot.
  • Broad language support: Supports a wide array of languages including TypeScript, Python, Go, Rust, Java, C++, and more.
  • MCP Server integration: Provides 22 tools for agent frameworks to perform merge analysis, entity inspection, and live coordination via a CRDT.
  • Deterministic merge: Operates as a stateless 3-way merge driver compatible with Git and Jujutsu (jj).
  • Detailed conflict markers: Provides specific reasons why a merge was refused (e.g., which internal guard failed) and the entity involved.

Related

  • Project
  • Project
  • Project
  • Dispatch
  • Project