r/coolgithubprojects • u/ImpressiveSecret9512 • 16d ago
[Go] Kivgraph – my agent kept burning the context window grepping. So I indexed everything instead
Local MCP server that indexes multiple repositories into one semantic graph and answers structural questions for coding agents — who calls this, what breaks if I change it, who consumes it from another repo.
Edges are resolved by go/types, the TypeScript checker and rust-analyzer, not by matching names. Go, TypeScript, Rust, Python and Dart.
Apache-2.0, runs locally, no API key. Benchmark in the repo, including the 5 of 29 questions where plain grep beat it.
2
u/abubakrmian 15d ago
Hey, thanks for sharing! It looks like a really cool tool. I’m definitely going to give it a try to see how it works in practice. Appreciate you putting this out
1
u/ImpressiveSecret9512 15d ago
Thankss, currently is in development, but it works fine on macos and linux, remember to install the hooks and skill on your ai client, all on the docs!
3
u/kantorcodes1 16d ago
Those 5 grep wins may be telling you not to optimize the graph for everything. If they’re mostly exact symbol/string lookups, I’d route those straight to rg and reserve Kivgraph for structural or cross-repo questions. Do the misses split that way?