
Memory Setup
Turn on vector memory search and folder structure so Moltbot/Clawdbot agents keep context across sessions instead of forgetting everything.
Overview
Memory-setup is a journey-wide agent skill that configures Moltbot/Clawdbot vector memory and MEMORY.md structure—usable whenever a solo builder needs persistent agent context before committing to long workflows.
Install
npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill memory-setupWhat is this skill?
- Enables memorySearch in clawdbot.json or moltbot.json with provider, sources, and index modes
- Defines workspace layout: MEMORY.md, memory/logs, projects, groups, and system folders
- Templates long-term MEMORY.md sections for user facts, projects, decisions, and preferences
- Documents config knobs: minScore, maxResults, hot index, and memory vs sessions sources
- Targets fixing goldfish-brain context loss with Voyage (or configured) embedding search
- 5 memory folder roles (logs, projects, groups, system, root MEMORY.md)
- 6 documented memorySearch config settings
Adoption & trust: 1.4k installs on skills.sh; 609 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your coding agent forgets prior decisions and project context every session—the goldfish-brain problem—with no memorySearch or file layout in place.
Who is it for?
Indie builders on Clawdbot/Moltbot who want durable MEMORY.md plus indexed search without designing the folder scheme from scratch.
Skip if: Generic Claude Code memory plugins unrelated to Clawdbot/Moltbot, or teams that forbid storing session content in local vector indexes.
When should I use this skill?
Setting up memory, fixing goldfish brain, or helping users configure memorySearch in Moltbot/Clawdbot config.
What do I get? / Deliverables
You get enabled memorySearch settings, a documented workspace memory tree, and an initialized MEMORY.md ready for daily logs and retrieval.
- Configured memorySearch block
- Workspace memory directory tree
- Initialized MEMORY.md template
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Enable memorySearch and create MEMORY.md when you first wire Clawdbot into your repo workflow.
Re-index memory after a release so the agent recalls launch decisions during code review.
Store recurring user support preferences in memory/system so replies stay consistent.
Append daily logs after incidents so the next debug session retrieves lessons learned.
Capture competitor and audience notes in memory/projects before you commit to a build scope.
How it compares
Bot-specific memory bootstrap—not a general RAG pipeline skill or an MCP memory server listing.
Common Questions / FAQ
Who is memory-setup for?
Solo builders using Moltbot or Clawdbot who need step-by-step memorySearch config and a sane MEMORY.md plus daily log layout.
When should I use memory-setup?
At first agent install in Build, when fixing forgotten context in Ship review loops, or when scaling Grow content work that depends on stable user preferences stored in memory.
Is memory-setup safe to install?
Check the Security Audits panel on this page; enabling session indexing can persist sensitive chat text locally—review provider keys and sources.
SKILL.md
READMESKILL.md - Memory Setup
# Memory Setup Skill Transform your agent from goldfish to elephant. This skill helps configure persistent memory for Moltbot/Clawdbot. ## Quick Setup ### 1. Enable Memory Search in Config Add to `~/.clawdbot/clawdbot.json` (or `moltbot.json`): ```json { "memorySearch": { "enabled": true, "provider": "voyage", "sources": ["memory", "sessions"], "indexMode": "hot", "minScore": 0.3, "maxResults": 20 } } ``` ### 2. Create Memory Structure In your workspace, create: ``` workspace/ ├── MEMORY.md # Long-term curated memory └── memory/ ├── logs/ # Daily logs (YYYY-MM-DD.md) ├── projects/ # Project-specific context ├── groups/ # Group chat context └── system/ # Preferences, setup notes ``` ### 3. Initialize MEMORY.md Create `MEMORY.md` in workspace root: ```markdown # MEMORY.md — Long-Term Memory ## About [User Name] - Key facts, preferences, context ## Active Projects - Project summaries and status ## Decisions & Lessons - Important choices made - Lessons learned ## Preferences - Communication style - Tools and workflows ``` ## Config Options Explained | Setting | Purpose | Recommended | |---------|---------|-------------| | `enabled` | Turn on memory search | `true` | | `provider` | Embedding provider | `"voyage"` | | `sources` | What to index | `["memory", "sessions"]` | | `indexMode` | When to index | `"hot"` (real-time) | | `minScore` | Relevance threshold | `0.3` (lower = more results) | | `maxResults` | Max snippets returned | `20` | ### Provider Options - `voyage` — Voyage AI embeddings (recommended) - `openai` — OpenAI embeddings - `local` — Local embeddings (no API needed) ### Source Options - `memory` — MEMORY.md + memory/*.md files - `sessions` — Past conversation transcripts - `both` — Full context (recommended) ## Daily Log Format Create `memory/logs/YYYY-MM-DD.md` daily: ```markdown # YYYY-MM-DD — Daily Log ## [Time] — [Event/Task] - What happened - Decisions made - Follow-ups needed ## [Time] — [Another Event] - Details ``` ## Agent Instructions (AGENTS.md) Add to your AGENTS.md for agent behavior: ```markdown ## Memory Recall Before answering questions about prior work, decisions, dates, people, preferences, or todos: 1. Run memory_search with relevant query 2. Use memory_get to pull specific lines if needed 3. If low confidence after search, say you checked ``` ## Troubleshooting ### Memory search not working? 1. Check `memorySearch.enabled: true` in config 2. Verify MEMORY.md exists in workspace root 3. Restart gateway: `clawdbot gateway restart` ### Results not relevant? - Lower `minScore` to `0.2` for more results - Increase `maxResults` to `30` - Check that memory files have meaningful content ### Provider errors? - Voyage: Set `VOYAGE_API_KEY` in environment - OpenAI: Set `OPENAI_API_KEY` in environment - Use `local` provider if no API keys available ## Verification Test memory is working: ``` User: "What do you remember about [past topic]?" Agent: [Should search memory and return relevant context] ``` If agent has no memory, config isn't applied. Restart gateway. ## Full Config Example ```json { "memorySearch": { "enabled": true, "provider": "voyage", "sources": ["memory", "sessions"], "indexMode": "hot", "minScore": 0.3, "maxResults": 20 }, "workspace": "/path/to/your/workspace" } ``` ## Why This Matters Without memory: - Agent forgets everything between sessions - Repeats questions, loses context - No continuity on projects With memory: - Recalls past conversations - Knows your preferences - Tracks project history - Builds relationship over time Goldfish → Elephan