nocturne_memory and ClawMem
These are competitors offering alternative approaches to agent memory persistence: nocturne_memory emphasizes graph-structured rollbackable memory as a replacement for Vector RAG, while ClawMem provides hybrid RAG search with on-device processing, forcing a choice between semantic graph-based vs. hybrid retrieval architectures for the same use case.
About nocturne_memory
Dataojitori/nocturne_memory
A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents. Say goodbye to Vector RAG and amnesia. Empower your AI with persistent, graph-like structured memory across any model, session, or tool. Drop-in replacement for OpenClaw.
Implements a graph-based memory architecture with SQLite/PostgreSQL backends, where AI agents can create, update, and rollback their own structured memories through MCP—eliminating vector RAG's semantic lossy compression and enabling condition-triggered disclosure of hierarchical knowledge graphs with human-auditable versioning. Includes a visual dashboard for memory exploration, diff review, and governance; integrates natively with Claude Desktop, Cursor, and other MCP-compatible frameworks as a direct OpenClaw replacement.
About ClawMem
yoloshii/ClawMem
On-device context engine and memory for AI agents. Claude Code and OpenClaw. Hooks + MCP server + hybrid RAG search.
Combines multi-signal retrieval (BM25, vector search, and graph traversal with reciprocal rank fusion) with composite scoring that decays stale memories while boosting frequently-revised and co-accessed notes, plus local GGUF model inference for decision capture and intent classification. Integrates across Claude Code hooks, MCP servers, and OpenClaw's ContextEngine plugin—all three write to the same local SQLite vault, enabling memory continuity across different agent runtimes without cloud dependencies.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work