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
Add graph-based knowledge memory to augment existing vector + keyword semantic search. The graph stores entities, relationships, and communities extracted from conversations, enabling multi-hop reasoning, temporal fact tracking, and cross-session entity linking.
Motivation
Current limitations of flat vector + FTS5 search:
No entity relationships (cannot answer "how is X related to Y?")
No multi-hop reasoning (cannot chain A->B->C)
No temporal fact tracking (cannot track "user preferred X, then switched to Y")
No contradiction detection (conflicting facts coexist)
No cross-session entity linking
Industry benchmarks (Zep/Graphiti, arxiv:2501.13956) show +18.5% accuracy on multi-session temporal reasoning and 90% latency reduction vs full-context approaches.
Summary
Add graph-based knowledge memory to augment existing vector + keyword semantic search. The graph stores entities, relationships, and communities extracted from conversations, enabling multi-hop reasoning, temporal fact tracking, and cross-session entity linking.
Motivation
Current limitations of flat vector + FTS5 search:
Industry benchmarks (Zep/Graphiti, arxiv:2501.13956) show +18.5% accuracy on multi-session temporal reasoning and 90% latency reduction vs full-context approaches.
Architecture
graph_entities,graph_edges,graph_communities) + Qdrant embeddings for entity/fact searchgraph-memory(opt-in, zero impact on existing pipeline)Design Documents
.local/plan/graph-memory-research.md.local/plan/graph-memory-architecture.md.local/plan/graph-memory-critique.mdImplementation Phases
Cross-Epic Dependencies (with #1195 Untrusted Content Isolation)
GraphStorewritesgraph_recall()outputRecommended order: #1207 before or with #1225; #1203 before or with #1226.
Follow-up Issues
Estimates