Alternatives
Products that do what MemoFS does
File-first memory runtime for AI agents.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19PL
How it works: - Storage uses one SQLite database file, plus a local LanceDB index of vectors. No need for a server, cloud services, or any API keys. - Retrieval is a hybrid approach using BM25 (rank-bm25) and vector-based search (sentence-transformers) combined with a co-occurrence graph of entities, using reciprocal rank fusion. The idea is to find the right memory, not the closest one. - It plugs into the agent's lifecycle via MCP: before the agent responds, relevant memories are added to its input; after each turn, decisions and new learnings are automatically recorded. No need to…
Jun 2026 · github.com
- 20AD
2025 · github.com
- 21YP
It's an biological inspired decay system for our memories with extended support of temporal reasoning. Created a CLI command to infer knowledge from the context stored in memory system without any token utilization or llm call. It comes with a memory dashboard to monitor and manage your memories it can be extended as audit trail for agents as well !
May 2026
- 22UM
I was frustrated that memory is usually tied to a specific tool. They’re useful inside one session but I have to re-explain the same things when I switch tools or sessions. Furthermore, most agents' memory systems just append to a markdown file and dump the whole thing into context. Eventually, it's full of irrelevant information that wastes tokens. So I built this local memory layer that unifies memory across agents. Instead of a flat file, it builds a structured knowledge graph of "memory notes" inspired by the paper "A-MEM: Agentic Memory for LLM Agents"…
Apr 2026 · github.com
- 23MC
Hi HN, I’ve been building AI agents and copilots, and kept running into a frustrating problem: they don’t fail loudly, they forget things quietly. Users re-explain preferences, agents contradict earlier responses, and context resets without any clear visibility into why. I built Memograph CLI as a debugging tool to analyze conversation transcripts and show: - what the agent forgot - where continuity broke - contradictions and repeated context - estimated token waste due to re-prompting It works locally and supports plain text or JSON transcripts. Example: $ memograph Output: Cognitive Drift…
Feb 2026
- 24CO
So I've been building ClawMem, an open-source context engine that gives AI coding agents persistent memory across sessions. It works with Claude Code (hooks + MCP) and OpenClaw (ContextEngine plugin + REST API), and both can share the same SQLite vault, so your CLI agent and your voice/chat agent build on the same memory without syncing anything. The retrieval architecture is a Frankenstein, which is pretty much always my process. I pulled the best parts from recent projects and research and stitched them together: [QMD](https://github.com/tobi/qmd) for the…
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →