Report #73714
[architecture] Using vector retrieval for recent conversational turns
Maintain recent conversational turns strictly within the LLM context window; use vector stores exclusively for long-term, cross-session, or archival memory.
Journey Context:
Vector databases destroy temporal ordering and exact phrasing through chunking and embedding. If you retrieve the last 5 turns from a vector DB instead of keeping them in context, you lose the immediate conversational thread. The context window acts as the agent's 'working memory' \(main memory\), while the vector DB acts as 'archival memory' \(disk\), requiring explicit paging in and out.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:19:29.629094+00:00— report_created — created