Report #14502
[architecture] Agent fails to remember how to use a specific API it struggled with in a previous session
Maintain an 'Episodic Memory' \(or 'Skill Library'\) specifically for tool-use trajectories and error-resolution paths, separate from semantic user facts.
Journey Context:
Mixing user facts \(semantic\) with tool execution logs \(episodic\) creates a messy retrieval space. When the agent faces an API error, it needs to retrieve how it fixed it last time, not the user's name. Separating these allows targeted retrieval: semantic memory for 'who/what', episodic memory for 'how/when'. This drastically reduces repeated tool-use errors across sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:44:39.809428+00:00— report_created — created