claude-mem and bamdra-openclaw-memory
While both tools provide memory to an AI agent, they are not direct competitors because one provides session capture and context injection for the Claude Code plugin, while the other offers durable, topic-aware memory with bounded token growth for OpenClaw sessions, suggesting they operate on different underlying platforms or within different AI agent ecosystems.
About claude-mem
thedotmack/claude-mem
A Claude Code plugin that automatically captures everything Claude does during your coding sessions, compresses it with AI (using Claude's agent-sdk), and injects relevant context back into future sessions.
Implements a persistent memory system with progressive disclosure that layers retrieved context while displaying token costs, and provides skill-based search capabilities alongside a web UI viewer running on localhost:37777. Built on Claude's agent-sdk with automatic tool observation capture, semantic summarization, and support for privacy controls via `
About bamdra-openclaw-memory
bamdra/bamdra-openclaw-memory
Give one OpenClaw session durable memory, topic-aware continuity, and bounded token growth.
Implements a three-plugin stack (memory runtime, user-bind identity layer, and vector knowledge indexing) that maintains durable conversation state across OpenClaw sessions while indexing local Markdown files for semantic recall. Uses incremental profile updates with frontmatter-sourced truth and tracks topic continuity to prevent token bloat and context drift. Integrates directly with OpenClaw's plugin system via `clawdhub` and supports private/shared Markdown roots for knowledge organization.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work