OpenClaw Memory

Privacy-first memory enhancement for OpenClaw.

OpenClaw Memory turns local memory from a hidden background behavior into a visible, manageable workspace. It keeps Markdown as the source of truth, uses a local vector index for fast retrieval, and adds setup, audit, health, and governance layers that feel like a real product instead of a plugin demo.

Screenshots

Overview

Library

Audit

Settings

What It Does

• Stores explicit memories with Markdown + local index dual-write
• Captures high-confidence implicit memories for identity, preference, project, and instruction signals
• Uses hybrid retrieval with vector, keyword, recency, and optional rerank
• Adds strength, pinning, confirmation, suspicious-audit, and source balancing
• Gives users a built-in console to inspect, search, edit, pin, confirm, export, and delete memories
• Verifies commercial licenses locally without sending memory data to your server

Why It Is Different

Most memory plugins stop at “store and retrieve.”

OpenClaw Memory is designed as a complete local memory workspace:

• Local-first: memory stays on the user's machine
• Product-grade setup: guided activation and model onboarding
• Strong retrieval: hybrid scoring, rerank, de-duplication, source balancing
• Trustable operations: health checks, audit flow, suspicious memory review
• Safer memory quality: strength, pinning, confirmation, and suspicious handling

Core Surfaces

• Overview: health, memory volume, recall volume, pinned memories, suspicious count
• Library: search, filters, table workspace, drawer inspection, batch actions
• Audit: suspicious-memory inbox, confirm or reject flow, activity log
• Settings: reconfigure setup, rebuild index, export data, maintenance actions

Setup Flow

The normal setup path is intentionally short:

1. License
2. Model
3. Complete

Users should not need to edit config files for the common path.

Install

Recommended npm flow:

openclaw plugins install @lycdev/openclaw-memory

Then open:

/memoryhybrid

If you distribute a tarball instead of publishing to npm:

openclaw plugins install .\openclaw-memory-<version>.tgz

Runtime URLs

• primary page: /plugins/memory-hybrid-sync
• aliases:
  • /memoryhybrid
  • /memory-console
  • /memory-hybrid-sync
• install verification endpoint: /memoryhybrid/api/bootstrap

Packaging

Published artifacts are no longer meant to expose the full TypeScript source tree.

This repo now builds a minified + obfuscated runtime bundle at:

• dist/index.js

Build it with:

npm run build

Generate customer artifacts:

powershell -ExecutionPolicy Bypass -File .\package-release.ps1

Generate customer artifacts plus npm tarball:

powershell -ExecutionPolicy Bypass -File .\package-release.ps1 -PackNpm

Publish

You still need npm and GitHub credentials on the publishing machine.

See:

• PUBLISHING.md

Health & Tests

Health:

• powershell -ExecutionPolicy Bypass -File .\gateway-health.ps1
• powershell -ExecutionPolicy Bypass -File .\gateway-health.ps1 -EnsureRunning
• powershell -ExecutionPolicy Bypass -File .\gateway-health.ps1 -Restart

Tests:

• powershell -ExecutionPolicy Bypass -File .\smoke-test.ps1
• powershell -ExecutionPolicy Bypass -File .\ui-smoke.ps1
• npx -y tsx .\management-test.ts

Product Docs

• PLUGIN_INTRO.md
• PRODUCT_PRD.md
• PRICING_AND_LICENSE.md
• ARCHITECTURE.md
• ROADMAP.md
• LICENSE_WORKFLOW.md