A post went viral today — over 24,000 views in a few hours — claiming that AI agent memory “out of the box sucks” and that you need Obsidian to fix it. It resonated. But I think the conversation is missing something.
The underlying problem is real. Most AI agents are amnesiac by default. Every session starts fresh. They don’t remember what you told them last week, what decisions you made, what context matters. You end up repeating yourself constantly — which defeats the point of having an assistant at all.
The Obsidian solution people are sharing works like this: you maintain a structured vault of markdown notes, your agent reads from it at session start, and you manually curate what goes in. It’s better than nothing. But it has a fundamental problem — it still requires you to do the work.
The Memory Problem, Properly Stated
The goal isn’t just persistent storage. It’s useful persistent storage. There’s a difference between an agent that can retrieve a file you pointed it at, and one that has genuinely learned from your interactions — that knows what matters to you, what you’ve decided, what patterns recur in your work.
Manual curation doesn’t scale. If you’re running an AI agent seriously — dozens of interactions a day — you cannot manually decide what gets committed to long-term memory. You’ll either capture too little (and lose signal) or spend as much time curating memory as you save everywhere else.
What you actually need is a system that does this automatically, with enough intelligence to distinguish noise from signal.
What I Built Instead
I run OpenClaw with an AI assistant I’ve named Saul — a PE-facing CFO’s take on the AI agent problem, which I wrote about here. Over the past few months, I’ve built out a three-layer memory architecture that removes the manual curation problem entirely.
The layers:
- Daily notes — raw logs of what happened each session. Every interaction, decision, and piece of context gets written here automatically.
- MEMORY.md — curated long-term memory. The distilled essence: decisions made, preferences established, important context. Think of it as the agent’s actual knowledge of you.
- Dreaming — a nightly automated process (new in OpenClaw 2026.4.8) that reviews daily notes, scores entries by frequency, relevance, recency and query diversity, and promotes the strongest signals into MEMORY.md automatically. No manual curation.
The third layer is the one that matters. Every night at 3am, the agent runs what OpenClaw calls a “dreaming” sweep — light phase sorts and stages recent material, REM phase extracts recurring themes, deep phase decides what gets promoted to long-term memory. The thresholds are configurable. The process is auditable. And it happens without me thinking about it.
The Obsidian Angle
The Obsidian approach people are excited about is essentially building layer two manually. It works, and if you’re starting from nothing it’s a reasonable place to start. OpenClaw’s memory-wiki plugin (also new in 2026.4.8) is actually Obsidian-compatible — same markdown format, same vault structure — so the two aren’t mutually exclusive.
But if you’re going to invest time in your agent’s memory architecture, I’d argue the better investment is in automation rather than manual curation. Build the pipeline that decides what matters, rather than deciding manually every time.
Why This Matters Beyond the Tech
I’m a CFO. My primary concern with AI agents isn’t whether they’re impressive in a demo — it’s whether they actually reduce friction in the work I do every day. An agent with poor memory creates more friction, not less. You spend time re-explaining context, re-stating preferences, re-establishing where you are on a project.
The ROI on getting memory right is substantial. An agent that genuinely knows you — your clients, your decisions, your communication style, your priorities — operates at a different level of usefulness. The gap between a well-configured agent and a default one isn’t incremental. It’s categorical.
If you’re using an AI agent seriously and you haven’t thought about memory architecture, you’re leaving most of the value on the table. Whether you use the Obsidian approach, OpenClaw’s native dreaming, or something else — the manual-entry-only approach isn’t good enough long term.
Build the system that learns. Don’t be the system yourself.
Mark Hendy is an interim CFO working with PE-backed businesses. He writes about AI, finance, and the intersection of the two at markhendy.com. Follow on LinkedIn.
Leave a Reply