OpenClaw + MemorySync

Overview

Install openclaw-memorysync and your OpenClaw assistant remembers you across WhatsApp, Telegram, Discord, Signal and every other channel it lives on. The plugin takes OpenClaw’s exclusive memory slot: memories relevant to each message are injected before the reply (inside a hard time budget with fail-open behaviour — a slow network can never delay a chat), and after each successful run your message is sent to MemorySync, which stores only the durable facts in it (the assistant’s reply is not sent), with a content-hash seed so a replayed turn is not extracted twice. Seven tools, /remember and /recall commands that dispatch straight to the tools, and a real setup doctor: /memorysync-status detects the three traps that silently deactivate any OpenClaw memory plugin (slot not set, permission gates missing, allowlist exclusion) and prints the exact config to paste. A raw error never reaches your chat — the competitors’ tool results embed exceptions; ours answer with friendly text on every failure path, tested.

Setup status and requirements

Supported version

openclaw-memorysync 1.1.0

Last setup review

2026-08-24

Permissions

A MemorySync API key with read and write scopes.

Limits

Requires OpenClaw ≥ 2026.7.1 and Node.js ≥ 22. The memory slot is exclusive — setting it displaces the bundled memory-core (that is the point). Gateway restart required after install.

Capabilities

• Owns plugins.slots.memory — replaces memory-core with platform-grade memory
• Automatic recall before each reply: hard budget, TTL cache, fail-open
• Facts-only capture from your message — replays recognised, injected context stripped
• Seven tools that never surface raw errors; single-id delete only, secrets refused client-side
• /remember, /recall, /memorysync-status — command-dispatch straight to tools
• The status doctor detects slot/permission/allowlist traps with exact fixes
• Respects OpenClaw’s 2-second session-end drain budget: zero network there, by test
• Validated by @openclaw/plugin-inspector against the latest OpenClaw (Status: PASS)

Quick Start

openclaw plugins install npm:openclaw-memorysync
# wire the slot + permission gates in ~/.openclaw/openclaw.json, then:
openclaw gateway restart

# MCP-only alternative:
openclaw mcp add memorysync --url https://mcp.memorysync.io/mcp --transport streamable-http

Use Cases

Explore More