Compare/claude-mem vs MemPalace

AI tool comparison

claude-mem vs MemPalace

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

C

Developer Tools

claude-mem

Persistent cross-session memory for Claude Code — 10x cheaper context

Ship

75%

Panel ship

Community

Paid

Entry

Claude-mem is a plugin that automatically captures and compresses coding session context, then intelligently reinjects relevant memory into future Claude Code sessions. With 67K GitHub stars, it has rapidly become one of the most widely-adopted quality-of-life improvements for developers using Claude Code daily. The system hooks into five lifecycle events — SessionStart, UserPromptSubmit, PostToolUse, Stop, and SessionEnd — to capture observations and store them in an SQLite database with FTS5 full-text search, backed by a Chroma vector database for semantic hybrid retrieval. A real-time web viewer at localhost:37777 shows the memory stream live. Progressive disclosure layers memory retrieval with token cost visibility, and a "<private>" tag excludes sensitive content from storage. Beyond Claude Code, claude-mem works with Gemini CLI, OpenCode, and OpenClaw gateways, making it gateway-agnostic persistent memory. The AGPL-3.0 license with a PolyForm Noncommercial exception on the ragtime/ module means it's free for personal use but requires source-sharing for networked commercial deployments.

M

Developer Tools

MemPalace

Persistent cross-session memory for any LLM — local, free, 96% LongMemEval

Ship

75%

Panel ship

Community

Free

Entry

MemPalace is a free, open-source AI memory system that gives large language models persistent, cross-session memory. It accumulated over 43,000 GitHub stars within a week of launch — one of the fastest open-source AI project takeoffs of 2026. Unlike systems that use AI to summarize memories (lossy by design), MemPalace stores all conversation data verbatim and uses vector search via ChromaDB and SQLite to retrieve relevant memories. The storage metaphor is architecturally literal: people and projects become 'wings', topics become 'rooms', and original content lives in 'drawers' — enabling scoped search rather than flat corpus retrieval. Memory retrieval costs just ~170 tokens, making it practical even in cost-sensitive deployments. On the LongMemEval benchmark it scores 96.6% raw (100% in hybrid mode, though the hybrid methodology has faced some independent scrutiny). It runs entirely locally at zero API cost, meaning no cloud dependency and no privacy leakage. The project has been independently validated on production agentic workflows and is already being integrated into agent frameworks.

Decision
claude-mem
MemPalace
Panel verdict
Ship · 3 ship / 1 skip
Ship · 3 ship / 1 skip
Community
No community votes yet
No community votes yet
Pricing
Open Source (AGPL-3.0)
Open Source (MIT) / Free
Best for
Persistent cross-session memory for Claude Code — 10x cheaper context
Persistent cross-session memory for any LLM — local, free, 96% LongMemEval
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

If you're using Claude Code heavily, this is table stakes. The FTS5 + vector hybrid search means you stop re-explaining your codebase conventions every session, and the 10x token savings claim holds up in practice. The lifecycle hook architecture is clean and non-intrusive.

80/100 · ship

Verbatim storage avoids the lossy-summary trap that plagues most memory systems. ChromaDB + SQLite locally is a practical stack with minimal operational overhead, and the 170-token retrieval cost is genuinely low. Worth evaluating before paying for any memory-as-a-service layer.

Skeptic
45/100 · skip

The AGPL license with a PolyForm Noncommercial carve-out creates real ambiguity for commercial teams. And piping your entire coding session history into a local SQLite database raises legitimate data security concerns for enterprise work. Test thoroughly before using on proprietary code.

45/100 · skip

The 100% hybrid LongMemEval score was achieved through targeted fixes for specific failing test cases, and independent reviewers have flagged methodology concerns. 43K GitHub stars in a week is hype velocity, not production validation. Wait for real-world deployments before betting critical workflows on this.

Futurist
80/100 · ship

This is what personalized AI looks like at the tooling layer — not a vendor feature, but community infrastructure that makes agents progressively smarter about your specific context. The gateway-agnostic design means this pattern will outlast any single coding agent product.

80/100 · ship

Persistent local AI memory is the missing infrastructure layer in most agent architectures. MemPalace's hierarchical 'palace' structure — wings, rooms, drawers — is a more principled approach to memory organization than flat vector search, and it points toward how agents will eventually manage long-horizon knowledge.

Creator
80/100 · ship

For anyone using Claude Code to manage creative projects, writing systems, or content pipelines, the cross-session continuity transforms the experience from stateless assistant to genuine collaborator. The web viewer UI is a nice touch for understanding what your agent actually remembers.

80/100 · ship

Being able to pick up a creative project where you left it — with full context intact across sessions — fundamentally changes how AI fits into long-duration creative work. Local storage means zero privacy leakage. This is the boring infrastructure that unlocks actually useful creative AI workflows.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later

claude-mem vs MemPalace: Which AI Tool Should You Ship? — Ship or Skip