60,499
stars
+20+252+1,082
7,661
forks
310
watchers
1,912
prs
957
issues
19
releases
67
discussions
README
MemPalace Local-first AI memory. Verbatim storage, pluggable backend, 96.6% R@5 raw on LongMemEval — zero API calls. [![][version-shield]][release-link] [![][python-shield]][python-link] [![][license-shield]][license-link] [![][discord-shield]][discord-link] [!CAUTION] Beware of impostor sites. MemPalace has no other official websites. The only official sources are this GitHub repository, the PyPI package, and the docs at mempalaceofficial.com. Any other domain (including .tech, .net, or other .com variants) is an impostor and may distribute malware. Details and timeline: docs/HISTORY.md. [!IMPORTANT] Claude Code sessions expire in 30 days without auto-save hooks wired. Read this → Need the shortest recovery/setup path? Use the Claude Code retention setup checklist. --- What it is MemPalace stores your conversation history as verbatim text and retrieves it with semantic search. It does not summarize, extract, or paraphrase. The index is structured — people and projects become wings, topics become rooms, and original content lives in drawers — so searches can be scoped rather than run against a flat corpus. The retrieval layer is pluggable. The current default is ChromaDB; the interface is defined in mempalace/backends/base.py and alternative backends can be dropped in without touching the rest of the system. Nothing leaves your machine unless you opt in. Architecture, concepts, and mining flows: mempalaceofficial.com/concepts/the-palace. --- Install Agent-guided setup Install the MemPalace skills first, then ask your coding agent to set up MemPalace. The setup skill detects your system, installs the Python package, configures MCP, and asks whether you want a private local palace, a shared-brain hub, or a client connected to an existing hub: bash npx skills add MemPalace/mempalace The repository exposes three skills: mempalace for guided installation and operations, mempalace-recall for search-before-answer recall, and mempalace-task for logstream delegation. Installing a skill does not by itself install the MemPalace CLI or MCP server; the setup skill guides the agent through those system changes and verifies the live connection. During guided setup the agent can offer weekly stable-release checks. They are disabled by default, contact only PyPI when enabled, and never install updates automatically. Cached availability appears in scoped mempalace_status fields for the serving runtime and, when a local proxy is present, its client runtime, allowing the agent to explain the release and request authorization before showing an exact upgrade plan. Setup records whether the runtime came from uv tool, pipx, or pip so the plan never proposes an upgrade command for the wrong installation. Direct CLI setup MemPalace ships a CLI, so install it in an isolated environment to avoid PEP 668 errors on Debian/Ubuntu/Homebrew Pythons and to keep mempalace's deps (chromadb, numpy, grpcio, …) from conflicting with anything else in you
Top issues
#27Multiple issues between README claims and codebase39 comments · 2026-04-07#599There are too few rooms18 comments · 2026-04-11#1963Epic: concurrent-writer HNSW corruption — unified tracking for the recurring-divergence cluster (357, 1092, 1581, 1799, 1845, 1888, chroma#6975, …)16 comments · 2026-07-08#531Readme chromadb version differs from actual14 comments · 2026-04-10#408Plugin assumes python3 -m mempalace — breaks on modern Linux (PEP 668) and with uv/pipx12 comments · 2026-04-09#269Hybrid retrieval direction: make the palace wiring production-real without changing the conceptual design12 comments · 2026-04-08#1888Peer-writer lock (#1818/#1823) is incompatible with the multi-session daemon topology (#1270) + external hook/manual mines11 comments · 2026-06-27#1329Stop hook: 1.9 TB palace bloat + ChromaDB Rust bindings segfault despite #1231 fix10 comments · 2026-05-03
Discussions
#2863I would like to contribute... i have created a Gmail Adapter...0 comments · 2026-10-18#2680Six months of research on MemPalace, and the one thing it couldn't do: a shared instance for a small group0 comments · 2026-10-05#2671One hub for every machine: a shared-brain setup, and a "new" Claude Code plugin for the client side0 comments · 2026-10-04#2585Hosted memory backend as a benchmark baseline?0 comments · 2026-09-23#2578Sharing a read-only dashboard for the palace (screenshots inside)0 comments · 2026-09-23#2570MAQS — open audit checklist for verbatim + hybrid memory systems0 comments · 2026-09-21#2566SeoPalace: an independent lexical layer on top of MemPalace (and a question about the name)0 comments · 2026-09-21#2543Optional lifecycle and release visibility for MemPalace0 comments · 2026-09-18
Latest release
v3.11.0 — audit, repair and opt-in EmbeddingGemma 2 v3.11.0 2026-10-14A palace can now be audited and repaired in guided steps, and EmbeddingGemma 2 arrives as an opt-in embedder with native image, audio and video search. Every palace records the embedding model that built it and refuses to open with a different one. Conversation mining stops discarding text, status, search, wake-up and hub mines stay responsive on large palaces, and a round of correctness fixes from the 3.11 review hardens metadata updates, recovery and HTTP validation. Upgrade notes - The first conversation mine after upgrading re-mines each conversation file it covers, once. The exchange c