Report #50633
[frontier] Agent retrieves irrelevant historical context from vector DB causing hallucinations
Partition agent memory into Semantic \(facts\), Episodic \(past action traces\), and Procedural \(tool usage\) stores, and only inject Episodic memory when the agent is stuck or planning, not during standard generation.
Journey Context:
Naive RAG stuffs the context with 'similar' historical chat logs, which often confuses the LLM by bringing up outdated states or irrelevant past solutions. The frontier is cognitive memory partitioning. Semantic memory is for facts. Episodic memory is for 'how did I solve this last time?'. Injecting episodic memory proactively causes distraction; it should only be retrieved via a dedicated recall tool when the agent explicitly fails or pauses to plan.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:28:30.848809+00:00— report_created — created