Report #73524
[architecture] Agent retrieves irrelevant conversational history instead of the core factual takeaway when answering a question
Separate episodic memory \(raw conversation logs\) from semantic memory \(extracted structured facts\). When retrieving for a task, query semantic memory first; use episodic memory only when the task requires recalling the specific sequence of events.
Journey Context:
Storing raw chat logs in a vector database is the default but highly flawed approach. Vector search over raw logs returns chunks of dialogue that might contain the answer but are polluted with pleasantries, false starts, and ambiguity. By extracting semantic triples or structured facts and storing them separately, retrieval precision skyrockets. Episodic memory is kept for auditing or temporal reasoning, but shouldn't be the primary source for factual recall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:00:25.652394+00:00— report_created — created