OpenClaw Integration

How memories.sh solves OpenClaw's memory problem.

OpenClaw runs on a workspace pack, not a single instruction file. memories.sh keeps that full pack synced, searchable, and portable across tools so behavior stays stable over time.

OpenClaw Setup Guide Resource Guide For Agents (llms.txt)

OpenClaw Workspace

AGENTS + skills + memory files

Memories.sh Store

durable rules, facts, decisions

Agent Runtime

stable context at prompt time

Workspace SetSynced

AGENTS.md

SOUL.md

TOOLS.md

memory/*.md

skills/**/*

Retrieval Trace

rules::project_scopeMatched

facts::workspace_stateMatched

skills::tooling_policyMatched

decisions::execution_styleMatched

10+

Files Synced

1:1

Skill Parity

Realtime

Drift Checks

How It Works

Workspace-first memory pipeline for OpenClaw.

The sequence is simple: onboard OpenClaw once, generate workspace artifacts from memories, then keep the workspace synced as your memory base evolves.

Recommended flow

Recommended Flow (CLI)

Step 1: Install memories CLI

pnpm add -g @memories.sh/cli

Step 2: Initialize OpenClaw workspace

openclaw onboard

If this command is missing, install OpenClaw first from official install docs.

Step 3: Enter your project

cd your-project

Step 4: Initialize memories in project

memories init

Step 5: Generate OpenClaw AGENTS workspace file

memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force

Step 6: Generate skills from memories

memories generate agents

Step 7: Ensure OpenClaw skills directory exists

mkdir -p ~/.openclaw/workspace/skills

Step 8: Copy generated skills into OpenClaw workspace

if [ -d .agents/skills ]; then cp -R .agents/skills/. ~/.openclaw/workspace/skills/; fi

Step 9: Ingest workspace files (with runtime config)

memories files ingest --global --include-config

Step 10: Apply workspace files (force update)

memories files apply --global --include-config --force

Run top to bottom. For deeper setup context, see OpenClaw integration docs.

Why It Solves It

Memory stability for OpenClaw at operational depth.

memories.sh addresses root causes of OpenClaw memory drift: fragmented files, manual sync, and tool-specific lock-in.

Workspace contract sync

Carry OpenClaw's workspace files as one versioned set, not ad-hoc edits scattered across machines.

AGENTS + SOUL + TOOLS + memory/**

Structured local memory

Store rules, facts, and decisions in one searchable database so context is durable between sessions.

SQLite + semantic recall

Cross-agent portability

Keep OpenClaw behavior and reuse it in Claude Code, Cursor, Windsurf, and other integrations.

One source of truth

Skill reuse

Generate `.agents/skills/**/SKILL.md` and sync into OpenClaw workspace `skills/` with predictable structure.

No manual skill rewrites

Safe config sync

Include `~/.openclaw/openclaw.json` when needed while redacting secret-like fields from stored files.

--include-config support

Repeatable maintenance loop

Regenerate and re-apply workspace artifacts whenever memories change, so runtime instructions stay aligned.

Automatable refresh cycle

Command Pattern

Repeatable sync loop instead of manual drift fixes.

Run this when memories change to keep OpenClaw workspace instructions and skills aligned with your latest state.

Sync OpenClaw workspaceCLI

/docs/integrations/openclaw

Config-safe sync

Use --include-config when you need OpenClaw runtime config synced too.

openclaw-memory-refresh.sh

Canonical refresh workflow for OpenClaw workspace instructions and skills.

cd your-project
memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force
memories generate agents
if [ -d .agents/skills ]; then
  cp -R .agents/skills/. ~/.openclaw/workspace/skills/
fi

memories files ingest --global --include-config
memories files apply --global --include-config --force

Read OpenClaw Integration File Sync Docs

OpenClaw Workspace Coverage

The file set that memories.sh keeps coherent.

OpenClaw's workspace is a contract. This is the high-value set that memories.sh can ingest and apply so runtime behavior does not fragment.

Synced~/.openclaw/workspace/AGENTS.md

Synced~/.openclaw/workspace/SOUL.md

Synced~/.openclaw/workspace/TOOLS.md

Synced~/.openclaw/workspace/IDENTITY.md

Synced~/.openclaw/workspace/USER.md

Synced~/.openclaw/workspace/HEARTBEAT.md

Synced~/.openclaw/workspace/BOOTSTRAP.md

Synced~/.openclaw/workspace/MEMORY.md or memory.md

Synced~/.openclaw/workspace/memory/*.md

Synced~/.openclaw/workspace/skills/**/*

FAQ

OpenClaw memory integration, answered.

Practical answers for implementing and maintaining memories.sh with OpenClaw.

What exactly is the OpenClaw memory problem?

OpenClaw relies on a full workspace pack, not one file. As that pack changes across sessions and machines, behavior drifts. memories.sh keeps those instructions and skills synchronized from a durable memory source.

Is this AGENTS.md only?

No. The recommended workflow is workspace-first and includes AGENTS, SOUL, TOOLS, IDENTITY, USER, HEARTBEAT, BOOTSTRAP, memory files, and skills.

Does this replace OpenClaw onboarding?

No. Run `openclaw onboard` first so OpenClaw creates its workspace. Then memories.sh generates and syncs updates into that workspace.

Can I keep OpenClaw memory aligned with other agents?

Yes. memories.sh stores memory once and generates outputs for multiple integrations, so decisions and rules stay consistent when you switch tools.