OpenClaw Memory Kit

Quick Start

Use scripts/bootstrap-openclaw-memory.ps1 to generate the sharable workspace, config, env template, and launcher scripts.
Read references/architecture.md when you need the conceptual model behind the memory system.
Read references/generated-files.md when you need to explain or customize the generated output.
Read references/sanitization.md when the user wants to verify which private details must never be copied.

Default to an isolated target root such as ~/.openclaw-memory-kit unless the user asks to merge into an existing OpenClaw state directory.
Keep the base kit memory-focused. Treat Feishu, Telegram, WeChat, and Memos as optional follow-up integrations instead of required setup.
For the current tested OpenClaw build, install memory-lancedb-pro together with a matching local openclaw package inside the generated state directory. This keeps openclaw/plugin-sdk resolvable for the memory plugin on newer releases.
Never copy the source user's raw .env, live app IDs, channel bindings, private LAN addresses, personal scope names, or filesystem usernames. Use placeholders only.
Run the bootstrap script. Use -Force only when the user explicitly wants to overwrite an existing kit.
If the user wants a human-facing handoff, point them to the package-level OPENCLAW-MEMORY-KIT.md.