You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
graft build in WORKSPACE mode writes empty stats.json #433
When graft build runs in WORKSPACE mode (multi-repo federation, where graft/workspace.json lists child repos like bots, client, server), it successfully builds the index for each child repo but writes graft/.cache/stats.json at the workspace root with all zeros:
{
"nodeCount": 0,
"edgeCount": 0,
...
}
This causes the Claude Code statusline to show "graft · not built · run graft build" even though the build succeeded and all queries (graft ask, graft grep, MCP tools) work correctly.
Expected Behavior
The stats.json should aggregate the child repo totals. For example, a workspace with three repos should show totals like nodeCount: 35529, edgeCount: 30973, etc.
Additional Issues
graft skeleton from the workspace root fails with "no wiring graph" — it only works when run from inside a child repo.
Steps to Reproduce
Set up a workspace with child repos (e.g., bots, client, server in graft/workspace.json)
Run graft build from the workspace root
Observe: Build succeeds, child repos indexed, but graft/.cache/stats.json shows all zeros
Verify: graft skeleton fails from workspace root; queries work correctly
Picked this up — the workspace parent now aggregates the children graphs into the root stats.json at build time, and the sync child keeps those totals instead of overwriting them back to zeros. Draft: #858. (The skeleton-from-root half of the issue looks like a separate ask — federated skeleton — happy to take that as a follow-up if you want it.)
Activity
hr1juldey commentedon Nov 18, 2026
Picked this up — the workspace parent now aggregates the children graphs into the root stats.json at build time, and the sync child keeps those totals instead of overwriting them back to zeros. Draft: #858. (The skeleton-from-root half of the issue looks like a separate ask — federated skeleton — happy to take that as a follow-up if you want it.)
test(workspace): the trailhq#433 aggregate under adversarial attacks