mem9

Route OpenClaw mem9 install, reconnect, troubleshooting, and uninstall flows through structured guides.

1.2k|119|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/mem9-ai/mem9 --skill mem9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mem9
Source: https://github.com/mem9-ai/mem9/tree/main/site/public
Command: npx skills add https://github.com/mem9-ai/mem9 --skill mem9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mem9 provides persistent memory across sessions for OpenClaw, routing setup, troubleshooting, and uninstall flows to a single, safe workflow that preserves sensitive state while enabling recovery.

Core Features & Use Cases

  • Route first-time install and reconnect flows to SETUP.md, guiding users through safe config edits and validation.
  • Route troubleshooting and uninstall flows to TROUBLESHOOTING.md and UNINSTALL.md, keeping local state clean and reversible.
  • Preserve filtered utm_* parameters from remote SKILL.md URLs through the create-new flow and first restart.
  • Enforce OpenClaw 4.23+ permission for conversation access and ensure deterministic provisioning with read-back verification.

Quick Start

Run through the setup flow with SETUP.md to install or reconnect mem9, consult TROUBLESHOOTING.md for issues, and use UNINSTALL.md to remove mem9.

Frequently Asked Questions about mem9

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up persistent memory for OpenClaw across local and remote deployments?

Persistent memory for OpenClaw is configured by routing the first-time install or reconnect flow through a safe setup process that validates openclaw.json edits and verifies read-back before any gateway restart.

Can I safely uninstall a memory plugin from OpenClaw without losing sensitive state?

Yes, uninstalling an OpenClaw memory plugin uses a dedicated flow that keeps local state clean and reversible, preserving sensitive data while safely removing the persistent memory configuration.

Does OpenClaw persistent memory require a specific version for conversation access permissions?

Yes, OpenClaw persistent memory requires version 4.23 or higher to enforce conversation access permissions, ensuring deterministic provisioning and safe config flow with read-back validation.

What is the best way to troubleshoot OpenClaw memory plugin configuration issues?

Troubleshooting OpenClaw memory plugin issues involves routing to a dedicated guide that enforces allowed openclaw.json keys, offers dry-run previews, and ensures read-back validation before any gateway restart.

Why does my OpenClaw gateway restart fail after editing the memory configuration?

An OpenClaw gateway restart fails after editing memory configuration if allowed openclaw.json keys are invalid. The setup flow prevents this by enforcing read-back validation and offering dry-run previews before restarting.