memory-setup

Configure and validate OpenClaw memory recall with MEMORY.md files.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill memory-setup-yuyuxinli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-setup
Source: https://github.com/yuyuxinli/moodcoco/tree/main/industry-skills/memory-setup-openclaw
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill memory-setup-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This memory setup enables OpenClaw to recall decisions, preferences, and todos across sessions, providing durable context for better continuity.

Core Features & Use Cases

  • Automates the creation and management of persistent memory files (MEMORY.md and memory/yyyy-mm-dd.md).
  • Defines a simple workspace memory structure and guidance for enabling memorySearch across sessions.
  • Applies to OpenClaw workflows requiring long-term recall, context retention, and cross-session consistency.

Quick Start

Create MEMORY.md and daily memory files under memory/, enable memorySearch in the OpenClaw config, then restart the gateway to enable persistent recall.

Frequently Asked Questions about memory-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable persistent context recall across OpenClaw sessions?▼

To enable persistent context recall across OpenClaw sessions, you need to create a MEMORY.md file, organize daily logs under memory/YYYY-MM-DD.md, and configure the memorySearch block in your OpenClaw config before restarting the gateway.

What is the required file structure for OpenClaw memory persistence?▼

The required file structure for OpenClaw memory persistence includes a root MEMORY.md file for core decisions and a memory/ directory containing daily logs formatted as memory/YYYY-MM-DD.md to maintain cross-session continuity.

How do I configure the memorySearch block for OpenClaw workflows?▼

You configure the memorySearch block in the OpenClaw config by setting parameters like enabled, provider, includeDefaultMemory, maxResults, and minScore, which controls how memory_search and memory_get retrieve persistent context.

Why does OpenClaw fail to recall memory_search results after configuration?▼

OpenClaw fails to recall memory_search results when the gateway is not restarted after updating the memorySearch block or when the memory files do not follow the enforced MEMORY.md and memory/YYYY-MM-DD.md structure.

Can I retain long-term decisions and todos using OpenClaw memory?▼

Yes, you can retain long-term decisions and todos using OpenClaw memory by writing them to the persistent MEMORY.md file, ensuring your workflows maintain context retention and cross-session consistency.

Do I need to restart the gateway to apply OpenClaw memory configuration?▼

Yes, you must restart the gateway to apply OpenClaw memory configuration, as restart verification steps are enforced to validate that the memorySearch block and persistent recall are fully active.