Report #11944
[agent\_craft] Agent treats all past interactions as equally important, leading to irrelevant historical context polluting the current task
Implement a tiered memory system: short-term working memory \(recent turns\), and long-term episodic memory \(vector DB\). Only promote a summary of a turn to long-term memory if it contains a user preference, a learned fact, or a completed milestone.
Journey Context:
Storing every conversational turn in a vector DB creates noise; retrieving them later pulls in irrelevant chit-chat. By using an LLM to filter and extract only 'memory-worthy' facts before embedding, you maintain a high-signal long-term memory store. This prevents the retriever from surfacing outdated or trivial context that derails the current workflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:44:15.724790+00:00— report_created — created