OpenClaw Memory Journey: Built-in Search vs MemPalace for Real-Time Session Recall
A developer on r/openclaw shares their journey tuning AI memory for real-time session transcript recall on OpenClaw. Running on an Intel iMac (i7-4771, 16GB RAM) with OpenClaw 2026.6.8 and MemPalace 3.4.1, they've cycled through built-in memorySearch, QMD, and an MCP-based MemPalace with ChromaDB. The result: a pragmatic split strategy because no single system handles real-time indexing reliably.
Current Setup: Split Recall
Both systems are active. The split is enforced in workspace files (AGENTS.md, SOUL.md, MEMORY.md, TOOLS.md, USER.md, IDENTITY.md):
- Recent conversations → built-in
memorySearch(re-enabled today after a long disable) - Older/deep semantic search →
mempalace_search
The Indexing Pipeline
- Built-in: Indexes session JSONL via experimental
sessionMemorywith debounced delta thresholds. - MemPalace: Batch-indexes via cron every 2 hours (8am–10pm).
Both openclaw memory status and mempalace status show active index updates. Commands used for MemPalace mining:
# Mine session transcripts (conversations mode)
mempalace mine ~/.openclaw/agents/main/sessions/ --mode convos --wing sessions
Mine workspace files (config, memory, agents, etc.)
mempalace mine ~/.openclaw/workspace/ --wing workspace
These run from mempalace-reindex.sh every 2 hours via cron.
What's Still Broken
- Real-time session indexing is unreliable — MemPalace is purely batch/pull and doesn't watch file changes (even running every 5 minutes showed no improvement).
- Two search tools create confusion over which one the agent reaches for.
startupContextisn't loading dated markdown files into new sessions.- Symlink bug on Mac (MemPalace ≤3.3.4) skips JSONL files — even after upgrade to 3.4.1 the issue persisted.
Previous Attempts
The author tried QMD for better search and knowledge graphs, but each search spawned a new process and overwhelmed the Intel iMac. MemPalace was the MCP replacement, but batch-only indexing forced the split approach. At one point they disabled built-in search entirely to force single-source truth, but re-enabled it today to get recent session recall working.
Key Takeaways
Session conversations need to be indexed within 5–10 minutes of delta changes, based on actual session transcripts (not summarised markdown). New sessions should inject recent context automatically after the first prompt — neither system fully delivers this today.
📖 Read the full source: r/openclaw
👀 See Also
Guide: Running GitHub Copilot with Local LLM on Windows via Lemonade Server
A developer created a walkthrough for setting up GitHub Copilot to work with a local LLM on a Framework Desktop using Lemonade Server, addressing the lack of simple instructions for this configuration on Windows.
12 OpenClaw SOUL.md and STYLE.md Templates with Practical Lessons
A developer created 12 OpenClaw agent templates for common use cases, each following the official 4-section spec, and identified key lessons including the necessity of STYLE.md for defining communication patterns and the importance of specific boundaries over vague personality traits.
Post-Mortem: Claude Max + OpenClaw Billing Errors from Stale OAuth and Isolated Cron Jobs
OpenClaw agent breaks randomly due to stale OAuth token blacklisting the entire Anthropic provider and isolated cron jobs hitting the Extra Usage bucket. Full fix: remove manual profile, move cron to main session, clear billing lockout.
Opus 4.7 Broke 40% of Prompts; Fix Was Structuring CLAUDE.md and Skills
After Opus 4.7 degraded ~40% of prompts across 6 setups, a fractional head of AI fixed it by replacing ad-hoc prompts with structured Skill files, hierarchical CLAUDE.md, and separate memory files — reducing token usage 22% and iteration turns from 3-4 to 1-2.