Dist

OpenClaw 3.8+ 智能上下文管理与记忆系统插件

This plugin implements a local memory engine and mostly behaves as described, but check these before installing: - Packaging mismatches: the registry entry/metadata contains inconsistent names/paths and SKILL.md claims a bundled ONNX model (~90MB) that is not listed in the provided files. Ask the author or inspect the package to confirm the model file is actually included or whether the plugin will fall back to a simpler (less accurate) embedding method. - Persistent local storage: by default it creates/uses a SQLite DB at ~/.openclaw/memory/memories.db and will save extracted user/AI content and embeddings. If you don't want conversation content persisted, do not install or change dbPath to a controlled location or disable automatic saving via configuration. - Native dependencies: the package depends on better-sqlite3 and onnxruntime-node which install native binaries; review build steps, and install in an environment where you trust building native modules. - Configuration: you can limit exposure by setting a custom MEMORY_ENGINE_DB_PATH, disabling cleanup/autosave, or enabling debug to inspect behavior. If the missing model is a concern, request a release that includes the model or confirm the fallback behavior. Given the inconsistencies, I recommend obtaining a clear build/release artifact (or official npm package) and confirming presence of the model and manifest paths before trusting this plugin with sensitive conversations.

Package: memory-engine (mcp) Version: 2.0.0 Description: Context management plugin using Context Engine API The memory-engine package is a context management plugin for the OpenClaw framework. Its primary function is to provide a local long-term memory system for AI agents. It uses better-sqlite3 for local data persistence and onnxruntime-node to run a local embedding model (all-MiniLM-L6-v2) for semantic search and knowledge extraction. The code includes logic for context compression, rule-based tagging, and similarity-based deduplication. No evidence of data exfiltration, remote code execution, or unauthorized file system access was found. The package operates entirely locally, storing data in the user's home directory under a dedicated plugin folder.