Remembrane – agent memory in one SQLite file, zero dependencies
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…
In plain words
Remembrane is a library that gives AI agents persistent memory stored in a single SQLite file with no external dependencies. It's designed for developers who need agents to retain facts across sessions without running hosted services or vector databases. Key features include deterministic recall for reliable unit testing, transparent scoring for search results, and a complete journal of all changes for snapshots and diffs.
written from the facts on this page · September 2026
From the sources
Local-first memory for AI agents: one SQLite file, zero deps. Recency-aware exact recall, conflict detection, time-travel journal, MCP server. - satyasairay/remembrane
In the maker’s words, at launch
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 it's what I rely on most. Beyond that: it's one file you can copy, inspect, or delete, with no server or background process; every result can show its own score breakdown, so ranking isn't a black box; and every change is journaled, so you can snapshot the store and diff it later. It also exposes an MCP server, so an MCP-capable agent like Claude can use it directly, and there are LangChain and CrewAI adapters. It ranks by similarity plus recency, importance, and whether a memory has been useful before, and those weights are configurable, including turning recency off. There's also a check that flags when two memories contradict each other, but it's a heuristic, and I'd treat its output as candidates to review rather than ground truth. Limits, up front: the default embedder is lexical, not semantic, so for real semantic recall you plug in sentence-transformers or OpenAI with one line. It's meant for agent-scale memory, thousands of items rather than millions; past roughly 50k you've outgrown the design and should use a vector database. None of the recency or conflict ideas are novel either. Systems like Zep have done temporal memory for a while; my only claim is that you can get a useful version of it in a dependency-free file you can test. I did compare it to mem0, and I want to be clear about what that does and doesn't show. I ran mem0 in its no-LLM mode (infer=False) with the same embedder, so it only measures the storage and ranking layer, not mem0's LLM extraction, which is its main value. In that narrow setting remembrane was faster, used less storage, and returned updated facts more often because it accounts for recency. That's a substrate comparison, not a claim to be better at memory overall. The numbers, and the cases where my default embedder loses, are in BENCHMARKS.md, and it reproduces in a couple of installs. I've written up the known gaps as issues: the CrewAI adapter is a helper rather than a drop-in backend so far, the benchmark should be extended to a public retrieval dataset with no LLM calls, and recall could use diversity-aware re-ranking so it doesn't return near-duplicates. Contributions welcome. On disclosure: I wrote this with Claude, made the design decisions myself, and I maintain it. I also had a second coding agent try to break each release, which surfaced some real bugs, including a cache-coherence issue under concurrent writers and a counterexample to a packing-optimality claim I had made. Those are fixed and are now regression tests. I'd rather you judge the tests and the changelog than take my word for it. Happy to hear where it falls short.
Does the same job
all alternatives →
MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS524d ago · github.com · ▲70An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 27d ago · cactuscompute.com
Launched alongside, August 2026
the whole month →- TL
Life & fun · 10d ago · louisabraham.github.io
- SA
Hello HN! I found that picking out plausible but diverse skin tones for my digital art and game development projects was kind of difficult, and I got curious about if there was a way to define a color space that made it easy. I've built a color picker and procedural generation algorithm based on the space as well as a bunch of other fun js features and demos throughout the page that use the equations. If you find it interesting, I have lots of explanations of how I built it and what properties the space has. The methodology might be a bit shaky, but hopefully the result is as helpful for…
Life & fun · Aug 2026 · toneyalexander.github.io
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com