nowfound

Alternatives

Products that do what Persistent memory for Claude Code with self-hosted Qdrant and Ollama does

I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…

  1. 1RG

    Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…

    Oct 2025 · npmjs.com

  2. 2SC

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com

  3. 3

    Shared memory across all apps and LLMs. In Claude

    Jul 2026 · unabyss.com

  4. 4

    Switch from ChatGPT to Claude with import memory feature

    Mar 2026 · claude.com

  5. 5PM
  6. 6

    Comprehensive memory management for Claude Code

    Mar 2026 · codeyam.com

  7. 7

    Store, review, and share your Claude Code sessions

    Mar 2026 · bench.silverstream.ai

  8. 8PM

    This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks!

    Jan 2026 · github.com

  9. 9

    Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline. - raiyanyahya/recall

    Jun 2026 · github.com

  10. 10
    PMB211

    Stop re-explaining your project to AI coding agents

    Jun 2026 · pmbai.dev

  11. 11

    Persistent memory for AI coding agents

    Apr 2026 · contextpool.io

  12. 12

    Persistent memory for Claude Code, Codex & coding agents

    May 2026 · agent-memory.dev

  13. 13CM

    We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient. While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules. CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion…

    Mar 2026

  14. 14

    Persistent AI memory across Claude Desktop & Cursor IDE

    Oct 2025

  15. 15CM
  16. 16TR

    built this because I got tired of re-teaching Claude Code the same context every session. Preferences, decisions, “we already tried X,” “don’t touch this file,” etc. After a few days it starts to feel like onboarding the same coworker every morning. Most “agent memory” tools auto-save everything. That feels good briefly, then memory turns into a junk drawer and retrieval gets noisy. Total Recall takes the opposite approach: a write gate. Before anything gets promoted, it asks one question: “Will this change future behavior?” If not, it doesn’t get saved. How it works: Daily log first (raw…

    Feb 2026 · github.com

  17. 17IB

    I wanted to share a project I have been working on over the past week. It is a simple local memory system that saves your sessions into Markdown files, which can be viewed later. I developed this after using Claude Mem. I really enjoyed working with it, but it was consuming a lot of RAM, and each Claude session was becoming a major resource hog. I also tried other plugins and MCP solutions, but ran into similar issues, either slow performance or concerns about data being sent elsewhere. Because privacy was a big thing for me, I decided to build my own solution that keeps all data local.

    Feb 2026 · github.com

  18. 18

    One memory across OpenClaw, ChatGPT, Claude & Gemini

    Feb 2026 · maximem.ai

  19. 19

    Shared persistent memory across all your LLMs.

    Sep 2025

  20. 20

    Semantic search over your own Claude Code session history

    13d ago · github.com

  21. 21RA

    Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…

    Jan 2026 · github.com

  22. 22

    An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory

    25d ago · github.com

  23. 23

    Connect Itsuki once with one key. It extracts structured memories from any of 26 connected tools — assistants, agents, workflows — links each to the words it came from, and serves them back across all the rest.

    Jul 2026 · uml.gpmai.workers.dev

  24. 24CM

    Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode…

    Feb 2026 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →