Report #52951
[frontier] Vector-only agent memory retrieving semantically similar but relationally irrelevant context
Store episodic memories as vector embeddings but index relationships in a knowledge graph, traversing graph edges to fetch contextually connected but semantically dissimilar facts
Journey Context:
Pure vector similarity retrieves 'apple' when querying 'fruit' but misses 'the budget approved yesterday' which is related via 'project X' node. 2025 production agents \(AutoGen, CrewAI\) adopt hybrid stores: vectors for semantic search, graph DBs for relationship traversal. Query does vector search for entry points, then graph traversal \(2-3 hops\) to fetch connected context. This replaces 'similarity = relevance' with 'relationship = relevance'. Tradeoff: higher write latency and graph DB operational complexity. Critical for long-horizon agents tracking entity relationships.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:22:29.094832+00:00— report_created — created