nowfound

Dev tools · alternatives · 2026

24 alternatives to Memori – Rust+SQLite persistent memory

Rust-powered persistent memory for AI coding agents

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.

  1. 1
    Memori▲168

    Persistent memory from agent trace, not just conversation

    May 2026 · memorilabs.ai · its alternatives →

  2. 2

    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 →

  3. 3
    Memoriq▲130

    Archive and search saved conversations from ChatGPT, Claude, Gemini, and Grok in one encrypted AI chat vault.

    Jun 2026 · memoriq.me · its alternatives →

  4. 4

    Persistent memory for Claude Code, Codex & coding agents

    May 2026 · agent-memory.dev · its alternatives →

  5. 5

    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 →

  6. 6

    I built LocalGPT over 4 nights as a Rust reimagining of the OpenClaw assistant pattern (markdown-based persistent memory, autonomous heartbeat tasks, skills system). It compiles to a single ~27MB binary — no Node.js, Docker, or Python required. Key features: - Persistent memory via markdown files (MEMORY, HEARTBEAT, SOUL markdown files) — compatible with OpenClaw's format - Full-text search (SQLite FTS5) + semantic search (local embeddings, no API key needed) - Autonomous heartbeat runner that checks tasks on a configurable interval - CLI + web interface + desktop GUI - Multi-provider:…

    Feb 2026 · github.com · its alternatives →

  7. 7

    Repo-native memory for coding agents

    Jul 2026 · github.com · its alternatives →

  8. 8

    One layer for memories, skills, and rules across any agent

    Feb 2026 · memories.sh · its alternatives →

  9. 9RG

    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 →

  10. 10

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

    Aug 2026 · github.com · its alternatives →

  11. 11

    This is a small library for giving an agent persistent memory without running any infrastructure. The whole store is one SQLite file, and the default install has no dependencies. I built it because whenever I wanted an agent to remember a handful of facts across sessions, the options were a hosted API, a vector database, or a framework, and that felt like too much for what is usually a few thousand short strings. The part I find most useful is that recall is deterministic, so you can write unit tests that assert what your agent remembers and run them in CI. I haven't seen that elsewhere and…

    Aug 2026 · github.com · its alternatives →

  12. 12
    PMB▲211

    PMB gives Claude Code, Cursor, Codex and Zed a real memory. Decisions, lessons and facts in one SQLite file on your disk. Offline, no API keys, no cloud.

    Jun 2026 · pmbai.dev · its alternatives →

  13. 13

    Most 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 →

  14. 14

    Enable agents to keep context & work across apps + sessions

    Jun 2026 · walrus.xyz · its alternatives →

  15. 15

    Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc. - CaviraOSS/LongMemory

    Dec 2025 · github.com · its alternatives →

  16. 16

    Coding agents don't have long-term memory. But you do have months of full-fidelity agent transcripts stored on your machine. A simple solution that goes a long way: ingest those transcripts and logs into a structured SQLite database, then search them with ranked text match. Everything is fully local and doesn't require anything fancy like a graph database or hosted memory service. This is the idea behind ctx, a Rust CLI that handles the ingestion and searching. We give our agents a skill that tells them to reference past sessions before working in an area. Usually we do this through an…

    Jul 2026 · github.com · its alternatives →

  17. 17

    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 →

  18. 18

    Markdown based AI agent memory with semantic search, hybrid retrieval, and offline-first sync between agents. - sqliteai/sqlite-memory

    Apr 2026 · github.com · its alternatives →

  19. 19

    Local-first AI memory layer for any LLM. Persistent knowledge graph, entity extraction, semantic retrieval. Works with Ollama, OpenAI, Anthropic, or any OpenAI-compatible backend. - zaydmulani09/mnemo

    Jun 2026 · github.com · its alternatives →

  20. 20

    Tell MemorySync a fact, reload the page, then ask for it back in your own words. No signup. Every API call shown in cURL, Python and Node.js.

    9d ago · memorysync.io · its alternatives →

  21. 21

    Persistent memory for AI agents. One API. Any platform

    Jun 2026 · github.com · its alternatives →

  22. 22
    Memora▲4

    AI coding agent. Single binary. Any model. Full audit trail.

    May 2026 · radotsvetkov.github.io · its alternatives →

  23. 23

    Open-source MCP server. #5 on LoCoMo. 100% local. MIT.

    May 2026 · totalmemory.dev · its alternatives →

  24. 24

    I've been working on Polign and built a small prototype around something I've been thinking about with agent memory. I have built a lightweight/stateless vector db + BM25 search which works really well with typed facts and structured queries. It uses your own S3, or GCS bucket as primary storage, and restarting a node is fairly quick. Demo + writeup: https://polign.com/blog-edge-agent-memory Live search demo: https://demo.polign.com Docs: https://polign.com

    Aug 2026 · polign.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 →