A support agent tells a customer their plan is still Enterprise, even though finance downgraded it last week. A coding copilot forgets a repo convention it learned yesterday. A personal assistant remembers your old home address and uses it to book a service call. These are not model problems. They are memory problems. Long-term memory for LLM agents is the layer that decides whether your system acts like software or a demo.
Most teams start with the obvious stack: embeddings, a vector database, top-k retrieval, maybe a reranker, then a prompt that says “use the following context.” That can work for document search. It usually fails as agent memory.
The reason is simple. Memory is not just similarity. It is persistence, retrieval, grounding, and time.
What long-term memory for LLM agents actually needs
If you are building agents that interact over days or months, memory has to do four jobs well.
