Building a hybrid graph-and-vector representation of an entire codebase—mapping relationships and semantic summaries during ingestion—lets agents jump instantly between distant points in a 10-million-line codebase instead of burning tokens traversing files via grep alone.
Sidhant explains that Blitzy built a hybrid graph-and-vector map of the entire codebase as an 'anchor point,' letting agents traverse huge codebases instantly rather than burning tokens searching file by file with grep. ✦ AI generated
Sidhant Pardeshi · The TWIML AI Podcast · 2026-03-10 · original ↗
starts at this moment · 19:45
“I feel adequately painted the picture of the complexity that you're dealing with with the traditional workflow. Like what are the things that you can do to to overcome, you know, all these many challenges?”
we've built a hybrid between a graph and a vector, um, that where you have this ingestion process with let's say for example that where it understands the entire code base, maps out the relationships, does semantic summarization and aggregation. And now you have this map of the entire code base.
verbatim transcript · starts at 19:45
19:45these many challenges? So, one thing that, um, you know, we've done from the beginning is build an anchor point that the agents can use to ground themselves, um, in the code base and to find things across the code base. Like for example, we've built a hybrid between a graph and a vector, um, that where you have this ingestion process with let's say for example that where it understands the entire code
20:11base, maps out the relationships, does semantic summarization and aggregation. And now you have this map of the entire code base. So, if I I want to go from one point to another point that's like 10 million lines deep, I can do that instantly in one request rather than burn all these tokens to travel through different files and find the chain, all right? So, that's like one technique
20:31that really works. What you just described in a lot of ways like flies in the face of the way we've seen the traditional tooling evolve. Like we started with rag which was based on, you know, and you know, people don't think about it like this, but and to a large degree, you know, the early co-pilot versions were kind of rag based. It was like semantic, uh, you
20:54know, vector style, you know, searching across the code base and identifying chunks and passing that on as context. Uh, and then, you know, the thing that we're all excited about, you know, the codexes and the cloud codes, like they don't do that anymore. They just do grep, what you're saying, like doesn't really work at scale. Uh it it's Yeah, interesting to it's interesting to think about um you know, that uh
21:26the kind of give and take that's happening here. And you know, what you're saying is that you need more sophistication to operate, or at least what I'm interpreting you saying as that you need more sophistication to operate at you know, enterprise scale, large scale codebases, whatever, you know, we want to call this. See, you know, to to bring that to a question, you know, maybe do you have a sense for like