Graphiti and GraphRAG: choosing retrieval for AI agents

Compare temporal memory with GraphRAG, vector search and agentic code search, including Graphiti and Zep for tracking changing facts.

Player not loading? Watch on YouTube

This comparison revisits GraphRAG through retrieval costs and the questions a system needs to answer. The speaker describes the original Microsoft approach as expensive to index because it extracts entities, builds communities and generates summaries across the corpus. LazyGraphRAG moves expensive work to query time. The cited Microsoft results put its indexing cost at 0.1% of the original, though the speaker cautions that Microsoft also published the benchmark.

The discussion challenges the assumption that a graph always improves retrieval. Citing GraphRAG Bench, the speaker recommends vector search for simple factual lookups and graph approaches for connections across documents or corpus-wide themes. HippoRAG uses personalized PageRank, while PathRAG prunes paths to reduce irrelevant material. Their reported performance gains refer to particular comparisons, rather than universal advantages.

For code search, the speaker cites Boris Cherny's account of Claude Code replacing indexed retrieval with agentic search using grep and glob. This coding assistant example depends on exact matches and meaningful filenames; the speaker sees a weaker case for books and other dense narrative documents. Graphiti and Zep enter the comparison as temporal memory options for changing facts. The closing guidance favors matching retrieval to the workload, combining methods where useful, and passing a small corpus directly into the context window when it fits.