A truly capable agent doesn't just respond to the current message โ it remembers what happened before, knows what it's learned, and can retrieve relevant past context. This requires implementing memory deliberately, because LLMs themselves are stateless between API calls.
The three memory types
Working Memory (In-Context)
Everything in the current context window โ the conversation so far, system prompt, retrieved chunks, and tool outputs. Fast to access (already in context) but limited by context window size and resets every session.
Episodic Memory (Conversation History)
Stored records of past interactions โ summarized or verbatim. Lets the agent recall "last week you mentioned you prefer Python" or "we discussed this issue in March." Stored externally (database) and retrieved selectively into context.
Semantic Memory (Long-Term Knowledge)
Domain knowledge embedded and stored in a vector database. The agent retrieves the most relevant knowledge chunks at query time โ product documentation, policies, past solutions. This is the foundation of RAG.
Combining all three with MoltBot
When to use each type
- Working memory only โ Simple Q&A bots, single-turn tasks where session history doesn't matter.
- + Episodic โ Customer service agents, personal assistants, any use case where remembering the user's history improves quality.
- + Semantic โ Knowledge-intensive tasks: support bots, internal wikis, research assistants. Anywhere the agent needs to recall facts beyond what fits in context.
- All three โ Enterprise agents that need to know both the user's history AND the company's knowledge base simultaneously.
All three memory types on MoltBot
Episodic, semantic, and working memory โ configured per agent. 14-day free trial.
Start Free Trial โ