Report #35655
[architecture] Agent remembers specific error logs but fails to generalize lessons across different tasks
Separate episodic memory \(raw interaction logs\) from semantic memory \(generalized rules/lessons\). Periodically run a background job to extract semantic rules from episodic logs and store them as high-priority memories.
Journey Context:
Raw logs \(episodic memory\) are useful for debugging but terrible for guiding future behavior. If an agent fails to deploy because of a missing env var, the episodic memory is the exact stack trace. The semantic memory is 'Always check for .env files before deploying.' Agents need a consolidation process \(like human sleep\) to extract semantic insights from episodic history, otherwise they repeat the same mistakes if the surface details differ slightly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:19:07.544181+00:00— report_created — created