How OpenClaw Orchestrates Long-Term Memory

Files Are the Source of Truth Forget embeddings stored in some opaque vector database you'll never inspect. OpenClaw takes a radically transparent approach: Markdown files in your workspace are the memory. The model "remembers" precisely what gets written to disk. Nothing more. The architecture splits into two layers. Daily logs live at memory/YYYY-MM-DD.md — append-only notes that capture running context, decisions made, and operational details from each session. These get loaded automatically when you reconnect (today's and yesterday's files, specifically). The second layer is MEMORY.md : curated, durable facts. Preferences. Architectural decisions. The stuff that shouldn't decay. This design has a brutal honesty to it. If the agent "forgets" something, you can open the file and see exactly why — either it never wrote the memory, or the search failed to surface it. No magical retrieval failures hidden behind API abstractions. # memory/2026-02-22.md - User prefers bun over npm; always