Report #72099
[frontier] Agent loses long-term context in 100\+ turn conversations due to naive RAG chunking destroying temporal relationships
Replace vector chunk RAG with explicit episodic memory architecture: store conversation blocks as immutable episodes in archival memory, retrieve via structured search \(timestamp, entity, keyword\) before falling back to embedding search; use recall memory for working context and archival for deep history
Journey Context:
Naive RAG splits conversation history into semantic chunks, destroying causal and temporal relationships required for long-horizon tasks; agents forget critical constraints from 20 turns ago because chunks lack episode boundaries. Alternative: infinite context windows \(prohibitively expensive/slow\). Episodic approach treats conversation as append-only event log with structured metadata, enabling precise retrieval like 'what did user say about billing on Tuesday'. Tradeoff: higher storage cost, requires explicit memory management calls rather than automatic RAG.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:35:55.627131+00:00— report_created — created