Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/your-ai-agents-memory-problem-may-be-something-else.md

Platform Engineering

Your AI agent’s “memory problem” may be something else

Many failures blamed on an agent's memory actually come from three separate sources: workflow state, durable memory, and retrieved knowledge. Each one needs its own owner, lifecycle, and access rules.

The New Stack20 Nov 2026 · 7 min read · summary

article --summary

The summary

The piece argues that failures usually called memory problems come from three distinct context types: workflow state for resuming runs, durable memory for facts carried across sessions, and retrieved knowledge for the current request. A LangGraph checkpoint can resume a run but cannot decide what is worth remembering, so the application must enforce scope, validity, correction, and deletion for memories rather than leaving it to the prompt. Retrieval brings in outside evidence, but semantic similarity alone does not show that a source is current, authoritative, or permitted for the caller. The author treats LangGraph and LangChain as building blocks rather than systems of record or final permission boundaries, so clear ownership shows where to investigate when something breaks. Readers are encouraged to design recovery paths alongside the normal flow, such as resuming after a failed tool without repeating side effects, superseding stale memories, excluding deleted documents before generation, and tracing which layer produced a wrong answer. The suggested starting point is one small workflow, with each of the three context paths tested separately before they are combined in the agent loop.

Editorial note: This is a summary of an article first published by The New Stack. The full piece is on their site.

Reading now

Topic
Platform Engineering
Source
The New Stack
Published
20 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.