Written by an engineer who runs this system daily
THE AI MEMORY GUIDE

Your AI Keeps
Forgetting Everything.

A step-by-step system for building persistent memory across Obsidian, OpenClaw, and Claude Code — so your AI actually knows who you are, what you're working on, and how you like things done.

# What your AI currently does:
$ openclaw chat
Agent: "Hi! I'm Claude. How can I help you today?"
You: <explains entire project from scratch, again>

# What it does after this guide:
$ openclaw chat
Agent: "Good morning. You've got a standup in 20 mins, the
RPG project deploy is pending, and you prefer dark roast."
£9 one-time · PDF + 10 templates · instant email delivery
✓ Works with free Obsidian ✓ OpenClaw + Claude Code ✓ ~30 min to first results ✓ Upload to your agent — it sets itself up
SOUND FAMILIAR?

Your AI has no memory. Every session starts from zero.

WHAT'S INSIDE

A 5-part guide to building the system properly.

Not theory. Not a blog post stretched to 10,000 words. A structured, opinionated guide to the exact setup that actually works.

PART 1
How AI Memory Actually Works
Context windows, compaction, memory flush — what's really happening when your agent "forgets". The 3-layer architecture: knowledge graph, daily notes, and tacit knowledge. Why you need all three.
PART 2
Setting Up Your Foundation
AGENTS.md, SOUL.md, MEMORY.md, and the secret weapon: TACIT.md. Obsidian vault structure. The one config line that connects your vault to OpenClaw's memory search. Setting up Obsidian as your AI's brain.
PART 3
Automation & Advanced Patterns
Nightly consolidation cron (with the config pattern most tutorials get wrong). Local embeddings at zero API cost. Claude Code integration. The Obsidian CLI as the bridge. Advanced command patterns for thinking, reflection, and idea generation.
PART 4
30-Day Implementation Playbook
Week-by-week plan from zero to a fully working memory system. Common mistakes and how to avoid them. Troubleshooting guide for when things break.
PART 5
Templates Walkthrough
10 ready-to-use templates — drop them into your workspace and start immediately. Each one explained: what it does, why it matters, how to customise it.
INCLUDED TEMPLATES

10 templates. Drop them in. Start immediately.

Everything from the guide, pre-built. You're not starting from a blank file.

AGENTS.md
Your agent's operating manual — role, rules, how it should behave and what it should check on startup.
USER.md
Who you are — name, timezone, work context, weekly routine. Your agent reads this every session so it knows who it's helping.
MEMORY.md
Structured long-term memory template with sections for facts, decisions, relationships, and ongoing context.
SOUL.md
Personality and values configuration. Defines tone, communication style, and what the agent should and shouldn't do.
TACIT.md
The secret weapon. Captures implicit preferences, working habits, and context your AI would otherwise never know.
daily-note-template.md
Daily note structure with proper sections — what happened, decisions made, things to remember, follow-ups.
HEARTBEAT.md
Heartbeat checklist template for proactive memory maintenance and periodic checks without clogging context.
project-TEMPLATE.md
PARA-structured project template with architecture decisions, open questions, and session-log bridge pattern.
consolidation-cron.json
Nightly memory consolidation cron config. Uses the correct sessionTarget pattern — the one most tutorials get wrong.
openclaw-memory-config.json
Full memory search config — extraPaths for Obsidian, local embeddings, hybrid search, temporal decay tuning.
WHO'S THIS FOR

Built for people who use AI seriously.

⚡
OpenClaw users who want persistent memory
You've installed OpenClaw, you're using it daily, but your agent forgets everything between sessions. This is the missing piece. You'll have a proper 3-layer memory system running within an afternoon.
💎
Obsidian power users who want AI integration
You've got an existing vault and you want your AI agent to actually use it — not just as a file system but as a knowledge graph it can read, write, and reason about.
⌨️
Claude Code users who want cross-session memory
Claude Code's CLAUDE.md is a start, but it's not a memory system. This guide shows you how to bridge Claude Code projects with your knowledge vault for genuine continuity.
🎥
People who've seen AI memory demos and want the actual how-to
Those AI memory demos look great — until you try to build it yourself. This guide gives you the exact folder structure, config files, and setup. Step by step.
WHY TRUST THIS

Built by someone who actually runs this system daily.

This isn't assembled from blog posts. I run this exact 3-layer memory architecture across my own Obsidian vault, OpenClaw setup, and Claude Code projects. The templates in this guide are the actual files I use.

I've iterated through broken configs, weird edge cases, and the inevitable moment where your AI confidently tells you something wrong because your MEMORY.md had a stale entry. The guide includes what I wish I'd known from the start.

The tools that power this system — OpenClaw's extraPaths indexing, the Obsidian CLI, local embeddings — all landed within days of each other. Nobody's written a comprehensive guide connecting them yet. This is the first one.

FAQ

Common questions.

OpenClaw (free), Obsidian (free), and Claude Code or a Claude API key. The guide is specifically built around this stack. You don't need any paid Obsidian plan — the free desktop app is everything you need. The core connection uses OpenClaw's built-in extraPaths config.
No. OpenClaw's built-in extraPaths config reads your local vault files directly — no cloud sync needed. You don't need Obsidian Sync (the paid cloud feature) at all. Just the free Obsidian desktop app.
About 30 minutes to get something working. An afternoon if you want to set up the full system including nightly consolidation and all three memory layers. The templates do most of the heavy lifting — you're filling in blanks, not writing from scratch.
Yes. Part 2 covers setting up your foundation from scratch, including Obsidian vault structure. You don't need an existing vault or prior Obsidian experience. The guide includes a recommended vault structure you can use directly.
The core concepts — MEMORY.md, AGENTS.md, daily notes, the 3-layer architecture — are tool-agnostic and work with any AI agent that reads a workspace directory. Parts 3–5 go deeper into OpenClaw and Claude Code specifics. If you're running a different setup, Parts 1 and 2 will still give you the architecture to adapt it.
No. Prompt engineering is about what you say. This is about what your AI reads. It's a file-based memory architecture — structured markdown files your agent loads at session start, automated cron jobs that consolidate daily logs into long-term memory, and a vault layout designed to be machine-readable. Much less glamorous than "prompting", much more effective.
It's £9. But more practically: the guide includes troubleshooting for common issues like extraPaths not indexing, restart gotchas, and the cron config that trips everyone up. The templates include comments explaining what each section does and why.
GET STARTED TODAY

Stop re-explaining yourself to your AI.

One afternoon of setup. Permanent memory. Your AI finally knows who you are.

£9 · one-time payment · no subscription
✓ PDF + templates.zip ✓ Instant email delivery ✓ Works with free Obsidian ✓ Instant access after purchase