I built my AI agents a local long-term memory. 4 months of daily use, one shipped app

Reddit r/AI_Agents Tools

Summary

An individual built a local long-term memory system for AI agents using markdown files and a local index, enabling persistent memory across sessions and including tests for false memories, with plans to potentially productize it.

Every AI tool forgets everything between sessions, and the built-in memory features live on someone else's server with someone else's rules. I got tired of that and built my own memory layer. What it is: plain markdown files as the source of truth. Readable, editable, mine forever. On top sits a local index for retrieval (vector embeddings, full text search, a graph linking related memories). The index is disposable, the files are permanent. Any agent can connect. After 4 months of daily use: My main agent recalls decisions from May and picks up projects mid-thought. I shipped an entire app this way and it never once started from zero. It keeps its name, personality and working rules across sessions, even across model switches. It maintains its own brain. Writes itself new rules when I correct it, consolidates old memories, forgets stale stuff. There's a trash bin, so I keep the final say. Password vault the agents can use but never see in plain text. I poisoned its memory with 20 believable lies to test it. Found real holes, fixed them. Now false memories get caught and quarantined instead of silently believed. It's Windows only, rough, built for myself. Now I'm trying to figure out if it should become a real product. So, honestly: A - I'd pay for this (free local core, one time price for the full version. What price feels fair?) B - I'd use it free, but wouldn't pay C - native ChatGPT/Claude memory is enough for me Every answer and every bit of honest feedback helps.
Original Article

Similar Articles

Last week I built an AI Agent, this week I added memory!

Reddit r/AI_Agents

A developer shares their experience building an AI agent with memory using the Anthropic SDK and TypeScript, explaining the differences between working, episodic, semantic, and procedural memory and the challenges of scaling memory for production.