← Back to Integrations
Integration · OpenClaw
XMemo for OpenClaw
Recall-first guidance and a native memory runtime give OpenClaw durable, user-owned context across sessions and compatible AI agents.
Available
Available on ClawHub · Native memory provider
Live XMemo Connector experience in Claude, ready for memory tools in the conversation.
Guidance and runtime, working together
The XMemo Skill and the OpenClaw Memory Plugin serve different, complementary roles. Best experience: install both.
XMemo Skill
For: OpenClaw users who want recall-first guidance and explicit standalone operations
Role: xmemo-skill
Status: Available on ClawHub
The Skill can run explicit XMemo operations through its bundled script (scripts/xmemo-skill.mjs): remember, recall, search, handoff, TODO, expense, and authentication diagnostics. The Skill does not replace OpenClaw's native memory slot or lifecycle integration, and it does not become a second memory slot.
OpenClaw Memory Plugin
For: OpenClaw users who want a native, active-memory backend
Role: xmemo-memory
Status: Available on ClawHub
Plugin ID: xmemo-memory. OpenClaw role: native kind: "memory" provider. Adds native lifecycle integration and can become OpenClaw's active memory backend for cloud-synced recall, search, TODOs, snapshots, timeline, and ledger/audit.
Guidance and runtime, working together
The Skill runs deliberate workflows and explicit standalone operations; the Plugin owns OpenClaw's native memory lifecycle.
XMemo Skill
Recall-first guidance + explicit operations
- Bundled runtime: scripts/xmemo-skill.mjs
- Remember, recall, search, handoff, TODO, expense, and authentication diagnostics
- Does not become OpenClaw's memory slot
XMemo Skill on ClawHub ↗
OpenClaw Memory Plugin
Native kind: memory provider
- Plugin ID: xmemo-memory
- Native lifecycle integration and active-memory recall
- Capture remains permission-gated
OpenClaw Memory Plugin on ClawHub ↗
Best experience: install both.
What each side is responsible for
Grouped by outcome, not by a flat list of tool names.
- Recall and memory: Search, retrieve, store, update, or forget durable XMemo memories from within OpenClaw, whether through the Skill's explicit standalone operations or the Plugin's native active-memory recall. Prompt: “Recall what we already decided about this project before we continue.”
- Plan and continuity: Create, list, and complete TODOs, record timeline events, and save or restore restart snapshots so work can resume across sessions. Prompt: “Save a restart snapshot and list the open TODOs for this project.”
- Governance and finance: Review Ledger monthly summaries and audit events or consolidation history. These operations require additional scope beyond the default memory:read/memory:write grant. Prompt: “Show me this month's Ledger summary and any pending audit events.”
- Resilience: A short-lived recall cache and a transient write outbox help the Skill's standalone runtime and the Plugin stay usable during brief connectivity gaps, for both hosted and self-hosted XMemo. Prompt: “Continue from the last verified checkpoint even if the connection was briefly interrupted.”
Install Skill + Plugin
The recommended path installs both the Skill and the Plugin. Best experience: install both. Hosted MCP remains an optional fallback after the native Plugin, not a replacement for it.
Recommended: personal desktop
Personal loginnpm install -g @xmemo/clientxmemo loginopenclaw skills install @xmemo/xmemoopenclaw plugins install clawhub:@xmemo/openclaw-memoryopenclaw xmemo status
Advanced: service or shared host
Environment-backed SecretRefPlace XMEMO_KEY in an environment or SecretRef visible to the OpenClaw gatewayopenclaw xmemo setup --env XMEMO_KEYConfirm plugins.slots.memory is xmemo-memoryopenclaw xmemo status --json
Permissions & Data Boundaries
autoCapture is off unless explicitly enabled.
External plugins do not receive conversation lifecycle content by default. Automatic capture only runs after allowConversationAccess is explicitly granted (hooks.allowConversationAccess = ["xmemo-memory"]), and it is meant to preserve high-signal messages, not a complete raw transcript. Messages that may contain secrets, injected content, or transport metadata should be skipped. Selecting xmemo-memory for plugins.slots.memory replaces the active memory provider; it does not migrate data from the previous provider.
- Authorization: All operations are authorized against the signed-in XMemo user, bucket, scope, team, and tool scope
- Local resilience: The recall cache and write outbox may contain memory content and should live in a protected user data directory
Developer Resources & Marketplace Status
ClawHub listings, source repository, and trust documentation.