Dev tools · alternatives · 2026
24 alternatives to Recall: Give Claude memory with Redis-backed persistent context
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…
Recall is an MCP server that gives Claude AI persistent memory using Redis and semantic search. Designed for developers who use Claude regularly for coding, it stores important context as searchable memories that… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline. - raiyanyahya/recall
Jun 2026 · github.com · its alternatives →
- 2
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 · its alternatives →
- 3
Switch from ChatGPT to Claude with import memory feature
Mar 2026 · claude.com · its alternatives →
- 4
OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc - mem0ai/mem0-chrome-extension
2024 · github.com · its alternatives →
- 5
- 6
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 · its alternatives →
- 7
Persistent memory for Claude, ChatGPT & Cursor. Free.
May 2026 · github.com · its alternatives →
- 8
Comprehensive memory management for Claude Code
Mar 2026 · codeyam.com · its alternatives →
- 9
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 · its alternatives →
- 10
Claude-Mem▲115AI agent memory, everywhere. claude-mem is open-source memory for Claude Code; cmem links it to any MCP client — Cursor, Codex, more — via one private link.
Dec 2025 · cmem.ai · its alternatives →
- 11
Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai · its alternatives →
- 12
Context Sync▲95Persistent AI memory across Claude Desktop & Cursor IDE
Oct 2025 · github.com · its alternatives →
- 13
I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…
Mar 2026 · github.com · its alternatives →
- 14
Memori▲168Persistent memory from agent trace, not just conversation
May 2026 · memorilabs.ai · its alternatives →
- 15CM
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 · its alternatives →
- 16
Shared persistent memory across all your LLMs.
2025 · teamlayer.xyz · its alternatives →
- 17
Tired of AI coding tools that forget everything between sessions? Every time I open a new chat with Claude or fire up Copilot, I'm back to square one explaining my codebase structure. So I built something to fix this. It's called In Memoria. Its an MCP server that gives AI tools persistent memory. Instead of starting fresh every conversation, the AI remembers your coding patterns, architectural decisions, and all the context you've built up. The setup is dead simple: `npx in-memoria server` then connect your AI tool. No accounts, no data leaves your machine. Under the hood it's TypeScript +…
2025 · github.com · its alternatives →
- 18
- 19
Hi HN. Live-Memory is an open-source Claude Code plugin / MCP server that serves as an always up-to-date memory of your codebase. It uses a separate, low-cost, large-context-window model to distill your repo's organization, conventions and general structure. It observes the primary agent's activity and builds an understanding of your repo passively over time. This way, when you start a new Claude Code session, your primary agent queries Live-Memory via one read-only ask_live_memory tool and bootstraps its understanding of the codebase for the particular task at hand, instead of…
Jul 2026 · github.com · its alternatives →
- 20
GPS▲83Memory layer for LLMs that stores repo rules + past lessons
May 2026 · github.com · its alternatives →
- 21
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…
Feb 2026 · github.com · its alternatives →
- 22
Timeglass turns everyday work into accurate timesheets attributed to the right client, project, and task. No timers, manual entry, or end-of-week reconstruction.
May 2026 · timeglass.ai · its alternatives →
- 23
recall▲7Stop wasting Claude Code tokens every time you resume.
Jun 2026 · recallplugin.dev · its alternatives →
- 24
Working memory for Claude Code - persistent context and multi-instance coordination - GMaN1911/claude-cognitive
Dec 2025 · github.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →