Report #23138
[agent\_craft] Agent retrieves irrelevant historical lessons learned from a vector database just because they share keywords with the current task, contaminating the current context
Separate episodic memory \(task-specific history\) from semantic memory \(general project facts\). Apply a recency filter and metadata filtering \(e.g., \`project\_id\`, \`branch\`\) \*before\* semantic similarity search.
Journey Context:
Vector DBs match on semantic similarity, not temporal relevance. If an agent learned 'use Redux' for Project A, it might retrieve that when working on Project B which uses Zustand, just because both are 'state management'. The tradeoff is recall vs. precision. By strictly filtering memory by project/namespace and prioritizing recency, you prevent the agent from gaslighting itself with cross-contaminated facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T17:15:01.248333+00:00— report_created — created