Report #13753
[agent\_craft] Agent uses vector database semantic search for all memory, retrieving irrelevant historical snippets that break the current logical flow
Separate episodic/working memory \(current task state, recent actions\) from semantic memory \(project knowledge, API docs\). Only query semantic memory when the current task requires domain knowledge not present in the local codebase.
Journey Context:
RAG is overused. When fixing a bug, the agent needs the stack trace and the relevant file \(episodic/working context\), not a vague paragraph from a design doc retrieved via embedding similarity. Injecting irrelevant RAG results distracts the LLM. Semantic retrieval should be a distinct, explicitly invoked tool, not a background process that pollutes every prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T19:43:06.492492+00:00— report_created — created