OpenClaw MEMORY.md: The File That Gives Your Agent Persistent Memory

Why OpenClaw Agents Forget

Every OpenClaw session is stateless by default. Yesterday's conversation isn't available today. Without a memory system, your agent starts fresh every time — no context, no continuity, no accumulated knowledge.

MEMORY.md solves this by storing information in a file that gets injected as context at the start of every session. It's not magic — it's a well-structured text file that your agent reads and writes.

The Three Sections Every MEMORY.md Needs

1. Iron-Law Rules

The non-negotiable constraints that govern agent behavior. These should never change without your explicit approval and a logged reason why.

Why "iron law"? Because these are rules your agent should follow even when its in-context reasoning suggests an exception. Naming them as iron law creates a category that the agent treats as non-negotiable rather than guidelines to weigh against situational factors.

Examples:

"Never spend real money without explicit approval."

"Never send messages to real humans without approval of the content."

"Three failed attempts on the same approach means stop and escalate."

2. Key Decisions Log

A running record of significant decisions: what was chosen, what was rejected, why. This is how your agent builds institutional memory. Without it, you'll relitigate the same decisions across sessions.

3. Lessons Learned

What worked, what didn't, and why. This is the compound interest section — small entries here prevent the same mistakes from repeating. Over 60 days, this becomes genuinely valuable institutional knowledge.

The Write Loop: What Most People Miss

Reading MEMORY.md is only half the system. Your agent also needs instructions to write to it — after completing significant work, after making a key decision, after hitting a failure worth preserving.

In your SOUL.md or AGENTS.md, add explicit instructions:

"Update MEMORY.md after completing significant work."

"Log every key decision with date and rationale."

"When you make a mistake, add it to Lessons Learned immediately."

Without the write loop, MEMORY.md becomes stale within a week.

The Nightly Consolidation Pattern

Advanced users pair MEMORY.md with a nightly consolidation job:

1. Agent reviews all work from the day

2. Extracts key decisions, lessons, and context worth preserving

3. Writes a dated summary to a daily log file

4. Updates the main MEMORY.md with anything that's now "long-term"

5. Pushes everything to GitHub as a backup

This creates a self-maintaining memory system. Your agent on day 60 has a fundamentally different operating baseline than on day 1.

Free Template

Download the free OpenClaw Starter Kit at agentickit.io/free — includes both SOUL.md and MEMORY.md templates ready to drop in and customize.

The full Solopreneur Operator Kit ($49) includes the complete system: AGENTS.md with autonomy tiers, HEARTBEAT.md with the nightly consolidation loop pre-built, and three production skill files.