{"slug": "search-all-your-past-claude-code-sessions-with-mempalace", "title": "Search all your past Claude Code sessions with MemPalace", "summary": "The MemPalace project released a local-first memory tool that stores Claude Code conversation transcripts verbatim and makes them searchable in plain language, addressing the fact that sessions expire after 30 days without auto-save hooks. The CLI, installable via uv or pipx, indexes history into a structured hierarchy of wings, rooms and drawers backed by ChromaDB, and exposes commands such as init, mine, search, wake-up and audit, plus an MCP setup path for coding agents. The README recommends scoping each project to its own wing and adding a rule to CLAUDE.md instructing the agent to run mempalace search before answering questions about past decisions.", "body_md": "Every Claude Code session starts from zero. You explain why you picked GraphQL, and three days later you explain it again. Worse, the MemPalace README warns that Claude Code sessions expire in 30 days unless you wire auto-save hooks. [MemPalace](https://github.com/MemPalace/mempalace) is a local-first memory tool that stores your conversation history verbatim and lets you search it in plain language. Here is the CLI route, with the commands from the README. The short version is on the [Deduped use-case page](https://dedupedai.com/use-cases/mempalace-mempalace/give-claude-code-searchable-memory-of-past-sessions/?utm_source=devto&utm_medium=article&utm_campaign=howto_mempalace).\n\nMemPalace stores conversation text as it was written. It does not summarize or paraphrase. The index is structured: people and projects become wings, topics become rooms, and original content lives in drawers, so you can scope a search instead of querying one flat pile. The default backend is ChromaDB, and per the README nothing leaves your machine unless you opt in.\n\nThe README recommends installing the CLI in an isolated environment, which avoids PEP 668 errors on Debian, Ubuntu and Homebrew Pythons:\n\n```\nuv tool install mempalace\n# or\npipx install mempalace\n```\n\nThere is also an agent-guided route. Install the skills, then ask your coding agent to set it up:\n\n```\nnpx skills add MemPalace/mempalace\n```\n\nThe setup skill detects your system, installs the package, configures MCP and asks whether you want a private local palace or a shared one. Installing the skill alone does not install the CLI or MCP server, so let the agent finish the guided setup.\n\nPoint it at a project:\n\n```\nmempalace init ~/projects/myapp\nmempalace mine ~/projects/myapp\n```\n\nThen mine your Claude Code transcripts:\n\n```\nmempalace mine ~/.claude/projects/ --mode convos\n```\n\nUse `--wing` to scope each project to its own wing, so a search about one app does not pull in another.\n\nAsk the question you keep re-explaining:\n\n```\nmempalace search \"why did we switch to GraphQL\"\n```\n\nYou get the original conversation back, not a summary of it. To start a new session with context loaded, run:\n\n```\nmempalace wake-up\n```\n\nTo check how well organized the palace is, run the read-only audit:\n\n```\nmempalace audit\n```\n\nA search tool only helps if the agent runs it. A prompt you can put in your first message or in `CLAUDE.md`:\n\nBefore answering any question about past decisions in this repo, run `mempalace search` with the question and quote the matching original text. Do not delete or move any transcript files.\n\nFor other ways to give Claude Code memory, compare with [claude-mem](https://dedupedai.com/use-cases/thedotmack-claude-mem/resume-claude-code-project-context/?utm_source=devto&utm_medium=article&utm_campaign=howto_mempalace), which summarizes instead of storing verbatim, or the Deduped page on [Docker MCP memory for Claude Code](https://dedupedai.com/use-cases/mempalace-mempalace/run-mempalace-as-a-docker-mcp-server/?utm_source=devto&utm_medium=article&utm_campaign=howto_mempalace).\n\nIf your sessions keep losing context, this is a 20 minute fix: install, mine, search, and add one line to your rules file.\n\nWant the setup commands for 50 AI repos people actually ship with? Get the free AI Repos That Actually Ship pack: [https://dedupedai.com/ship-pack/?utm_source=devto&utm_medium=article&utm_campaign=shippack](https://dedupedai.com/ship-pack/?utm_source=devto&utm_medium=article&utm_campaign=shippack)\n\n**Get one email every Monday with the week's hottest AI repos and exactly how to use them: [subscribe free at dedupedai.com](https://dedupedai.com/join/?utm_source=devto&utm_medium=article&utm_campaign=howto_mempalace)**", "url": "https://wpnews.pro/news/search-all-your-past-claude-code-sessions-with-mempalace", "canonical_source": "https://dev.to/dedupedai/search-all-your-past-claude-code-sessions-with-mempalace-30od", "published_at": "2026-10-30 19:13:06+00:00", "updated_at": "2026-10-30 19:20:49.697039+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "developer-tools", "agent-protocols", "ai-products"], "entities": ["MemPalace", "Claude Code", "ChromaDB", "Deduped", "claude-mem"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/search-all-your-past-claude-code-sessions-with-mempalace", "markdown": "https://wpnews.pro/news/search-all-your-past-claude-code-sessions-with-mempalace.md", "text": "https://wpnews.pro/news/search-all-your-past-claude-code-sessions-with-mempalace.txt", "jsonld": "https://wpnews.pro/news/search-all-your-past-claude-code-sessions-with-mempalace.jsonld"}}