AI · alternatives · 2026
24 alternatives to Memorist
An auditable, local-first memory engine for Open WebUI
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Memori▲168Persistent memory from agent trace, not just conversation
May 2026 · memorilabs.ai · its alternatives →
- 2
Agentmemory▲310Persistent memory for Claude Code, Codex & coding agents
May 2026 · agent-memory.dev · its alternatives →
- 3
- 4
DeltaMemory▲104Most AI agents forget everything between sessions. We built DeltaMemory to fix that. It's a cognitive memory layer that gives agents persistent recall, automatic fact extraction, and temporal reasoning — via a single SDK call. Key numbers: - 89% accuracy on LoCoMo long-term conversation benchmark - 50ms p50 retrieval latency - 97% cost reduction vs raw token re-processing Open source SDKs, works with any LLM stack. Currently in early access. Happy to answer questions about the architecture, benchmark methodology, or how we handle knowledge graphs.
Feb 2026 · deltamemory.com · its alternatives →
- 5RG
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…
2025 · npmjs.com · its alternatives →
- 6
OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc - mem0ai/mem0-chrome-extension
2024 · github.com · its alternatives →
- 7
YourMemory▲93This is a project that I have been building for a while now, YourMemory is a solution to agentic memory which focuses on pruning of noise rather than hoarding of data. In the current state of agentic memory most of the context is stored in the form of a MD file or is derived through a RAG model where you store each and everything. Both of the solution leads to bloated context which does not optimize the usage of any tokens. In this system we only keep relevant data in our memory and prune all the unnecessary data. The relevance of a data is derived through multiple factors such as recall…
Apr 2026 · yourmemoryai.vercel.app · its alternatives →
- 8
- 9
Memoriq▲130Archive and search saved conversations from ChatGPT, Claude, Gemini, and Grok in one encrypted AI chat vault.
Jun 2026 · memoriq.me · its alternatives →
- 10
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com · its alternatives →
- 11
Hey HN! I'm Arindam, part of the team behind Memori (https://memori.gibsonai.com/). Memori adds a stateful memory engine to AI agents, enabling them to stay consistent, recall past work, and improve over time. With Memori, agents don’t lose track of multi-step workflows, repeat tool calls, or forget user preferences. Instead, they build up human-like memory that makes them more reliable and efficient across sessions. We’ve also put together demo apps (a personal diary assistant, a research agent, and a travel planner) so you can see memory in action. Current LLMs are stateless…
2025 · github.com · its alternatives →
- 12
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…
2025 · github.com · its alternatives →
- 13
Captures and stores your chat from various AI platforms
Mar 2026 · ai-memory-beta.vercel.app · its alternatives →
- 14
Lossless long-term memory for a personal AI: never summarize, keep every line, put a timestamp on everything. - aru-labs/lossless-memory
Sep 2026 · github.com · its alternatives →
- 15
Enable agents to keep context & work across apps + sessions
Jun 2026 · walrus.xyz · its alternatives →
- 16
- 17
Hey HN! I built Memoripy, a memory layer for AI that adds short-term, long-term, and semantic memory capabilities to enhance LLM applications. It helps AI systems retain and prioritize past interactions, adapt over time, and respond with greater context and personalization. Memoripy uses semantic clustering to retrieve relevant memories, along with adaptive memory decay and reinforcement, so interactions stay fresh and context-aware. It’s designed for easy integration with OpenAI, Ollama, and other platforms—giving your AI applications dynamic memory management with minimal setup. Would love…
2024 · github.com · its alternatives →
- 18
Shared persistent memory across all your LLMs.
2025 · teamlayer.xyz · its alternatives →
- 19
Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc. - CaviraOSS/LongMemory
Dec 2025 · github.com · its alternatives →
- 20
- 21
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 →
- 22
memories.sh▲50One layer for memories, skills, and rules across any agent
Feb 2026 · memories.sh · its alternatives →
- 23
Memora gives AI the ability to recall memories during interactions, just like humans do subconsciously. For now, it’s just text-based memories, but our vision extends to the full spectrum of human memory: emotions, audio, video. Key Features: Built-in multi-tenancy for managing multiple organizations, users, and agents. Time-stamped memories to track how information evolves over time. Scalable, modular, and developer-friendly design. GitHub: https://github.com/ELZAI/memora Install: pip install memora-core We’re looking for feedback and contributions, let’s change how we…
2025 · github.com · its alternatives →
- 24
Hi HN, Working with multiple projects, I got tired of re-explaining our complex multi-node system to LLMs. Documentation helped, but plain text is hard to search without indexing and doesn't work across projects. I built Linggen to solve this. My Workflow: I use the Linggen VS Code extension to "init my day." It calls the Linggen MCP to load memory instantly. Linggen indexes all my docs like it’s remembering them—it is awesome. One click loads the full architectural context, removing the "cold start" problem. The Tech: Local-First: Rust + LanceDB. Code and embeddings stay on your machine. No…
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 →