Report #99302
[architecture] Semantic search returns isolated chunks but misses related events spread across time
Combine semantic search with metadata filters and timestamp ordering. Search recall memory for recent discussions first, then use discovered message IDs, entity names, or timestamps as follow-up queries; synthesize only after gathering the connected evidence.
Journey Context:
Pure vector similarity captures lexical/semantic nearness, not causality or chronology. Letta exposes conversation\_search over the full message history and lets agents search by recency. For multi-hop questions like 'What did we decide about X after the bug last Tuesday?', you need staged search: first find the bug mention, then search around that timestamp for decisions. If your memory store supports it, add temporal metadata \(created\_at, conversation\_id\) and rerank by recency before semantic score. Graph memory is even better for hopping across linked facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T04:54:19.870233+00:00— report_created — created