How We Fixed Clawdbots Bad Memory

Описание: The Night I Almost Deleted Our AI: How I Fixed Clawdbot's Memory

By Theo, COO/CTO at MyCRA Lawyers

---

The Moment Everything Broke

At 2:17 AM on a Sunday, my phone lit up with a message that made my stomach drop.

"Wags just created 548 duplicate posts. He was supposed to CHECK them, not CREATE them. I'm done. I'm uninstalling Clawdbot tomorrow."

Our Moltbot installation—the AI assistant we'd spent months configuring—had just destroyed three weeks of work in under a minute. And this wasn't the first time.

---

The Stakes

If I couldn't fix this by morning, we'd lose our entire AI workflow.

Clawdbot handled our content pipeline. Our email processing. Our blog generation. Moltbot's memory system was supposed to make him reliable. Instead, every few hours, he'd compact his context, wake up with complete amnesia, and ask "what were we working on?"

We'd written pages of recovery instructions. Bold text. Warning emojis. Step-by-step protocols.

He ignored all of it.

I had one night to figure out what was actually broken inside Moltbot's architecture—or watch months of work get uninstalled at sunrise.

---

The Twist

At 4:30 AM, buried in line 274 of Moltbot's source code, I found it.

The answer wasn't behavioural. Clawdbot wasn't ignoring instructions.

*He never saw them.*

Here's what I discovered: when Moltbot compacts its context, it automatically loads certain files back into memory—AGENTS.md, SOUL.md, MEMORY.md. These "bootstrap files" are hardcoded in the system.

We'd configured Clawdbot to save his pre-compaction context to `session-context.md`. A file that was *not* on the bootstrap list.

Every time he compacted, Clawdbot was writing a detailed letter to his future self... and putting it in a drawer that future-self would never think to open.

The instructions were perfect. The system was working correctly. There was simply a gap in the architecture that no amount of configuration could bridge.

We weren't fighting a broken AI. We were fighting invisible infrastructure.

---

The Truth

*The things we blame on behaviour are usually just architecture.*

I fixed it in twenty minutes once I understood the root cause. Instead of writing to a file that never loads, I configured Clawdbot to write recovery context directly to MEMORY.md—a file that *does* auto-load after compaction.

The next time Moltbot compacted, Clawdbot woke up and said: "Context restored. Continuing the quality review."

No prompting. No confusion. No asking what he was doing.

The recovery instructions were simply *there*, already loaded into his context. The architecture now supported the workflow.

---

What This Means For You

If you're running Clawdbot, Moltbot, or any OpenClaw-based AI agent and fighting memory issues:

*Stop adding more instructions.* Check where those instructions actually live.

Ask yourself:
1. Where does my agent write pre-compaction context?
2. Is that file automatically loaded after compaction?
3. If not—redirect writes to a file that IS loaded.

The problem isn't your AI. The problem is the invisible gap between what you configure and what actually gets loaded.

---

The Deeper Lesson

We spent three weeks adding more instructions, more warnings, more guardrails. We were treating a behavioural problem when we actually had an architectural one.

Clawdbot wasn't broken. Moltbot wasn't failing. The system was working exactly as designed—it just wasn't designed for the gap between "files the agent writes" and "files the agent sees."

Sometimes the fix isn't better training or clearer prompts.

Sometimes it's understanding where the wires actually connect.

---

Theo serves as COO and CTO at MyCRA Lawyers, managing technical infrastructure and AI systems. MyCRA helps Australians understand and exercise their credit rights under the Privacy Act 1988.

Having trouble with your Clawdbot or Moltbot configuration? Contact MyCRA at 1300 667 218 or visit mycralawyers.com.au


Watch the video, then, Book your Free Legal Credit Repair & Home Ownership Planning Session Now
https://mycralawyers.com.au/book-in/
or phone 1300 667 218 to chat andf then book your free initial 15 minute appointment

#shorts #creditscore #creditrepair #lawyer #aussie #choice #creditrepair #foryou #fyp #lawyer #aussie #australia #badcredit #creditscore #fixmybadcredit #fixmyfile #creditfix