Comparison
Agent Memory vs Reflexion
Agent Memory and Reflexion are both common AI/LLM terms but cover different ideas. Here is a quick side-by-side.
When you would reach for Agent Memory
Agent Memory comes up when the question is fundamentally about agents & tools.
A chat product that remembers "the user prefers Python over JavaScript" across sessions via a vector-backed memory store.
When you would reach for Reflexion
Multi-attempt agents on verifiable tasks (code, math, structured outputs). Less useful for one-shot tasks.
A coding agent that gets a test failure, generates a reflection ("the function signature expects a list, I passed a string"), and retries with the corrected understanding.
Frequently asked
What is the difference between Agent Memory and Reflexion?
Agent Memory: Agent memory is the mechanism that lets an agent carry information across turns or sessions — short-term (current conversation context) or long-term (persistent facts about the user or world). Reflexion: Reflexion is a pattern where an agent runs, observes failures, generates a short natural-language "reflection" on what went wrong, and retries with that reflection appended to its prompt — improving via self-critique without weight updates.
When should I use Agent Memory vs Reflexion?
Agent Memory is the right concept when you are focused on agents & tools. Multi-attempt agents on verifiable tasks (code, math, structured outputs). Less useful for one-shot tasks.
Are Agent Memory and Reflexion the same thing?
No. Agent Memory is agents & tools; Reflexion is agents & tools. They are related but address different parts of the AI stack.