Report #13012
[architecture] Should my coding agent remember past mistakes as raw logs \(episodic\) or extracted rules \(semantic\)?
Store raw interactions as episodic memory in a vector DB, but run a background consolidation process to extract generalized rules \(semantic memory\) into a structured knowledge base or system prompt.
Journey Context:
Episodic memory \(raw logs\) is great for exact recall but terrible for generalization and bloats the context. Semantic memory \(rules/facts\) is compact and highly reusable but loses the nuance of the original context. Agents need both: the episodic memory to answer 'what did I do last time?', and the semantic memory to answer 'what is the general rule for this codebase?'. Consolidation mimics human sleep cycles where episodic memories are distilled into long-term semantic knowledge.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:37:21.218529+00:00— report_created — created