Report #42568
[agent\_craft] Agent stores every interaction into a long-term vector store, retrieving irrelevant conversational fluff instead of coding facts
Split memory into Semantic \(facts, code snippets, API schemas\) and Episodic \(task history, user preferences\). Only embed and retrieve from Semantic memory for coding tasks.
Journey Context:
Naive RAG-based memory treats all text equally. 'I prefer tabs over spaces' is Episodic; 'The API endpoint for auth is /v1/login' is Semantic. Mixing them means retrieving a past greeting instead of a critical API schema. Separating them optimizes retrieval precision and prevents context pollution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:55:17.211693+00:00— report_created — created