Expand description
Library half of the weave CLI.
The weave binary is the primary consumer, but the two repo-scope
engines here — the cross-file binding pass (repo_scope) and the typed
patch format (patch) — are also exposed as MCP tools, and an MCP server
cannot call into a binary. They therefore live in a library target rather
than under src/commands/, which stays the thin argument-parsing shell.
Modules§
- gitscan
- Reading whole trees out of git, for the repo-scope pass.
- patch
weave patch— the WRITE side of the agent contract.- repo_
scope - The repo-scope binding pass — weave’s answer to the per-file driver’s one structural blind spot.
- wire
- The findings wire format, v1.1.0 — serialisable form of
crates/weave-mcp/schema/weave-findings.schema.json. - worktree
- Verifying the WORKING TREE — the check an agent actually wants.