{"author":"Nicole9","children":[{"author":"mikasisiki","children":[],"created_at":"2026-01-06T12:54:03.000Z","created_at_i":1767704043,"id":46511628,"options":[],"parent_id":46511540,"points":null,"story_id":46511540,"text":"Feels like file-system-style storage is pretty similar, conceptually, to Claude\u2019s current Skills design.","title":null,"type":"comment","url":null},{"author":"snasan","children":[],"created_at":"2026-01-06T12:58:00.000Z","created_at_i":1767704280,"id":46511668,"options":[],"parent_id":46511540,"points":null,"story_id":46511540,"text":"There are quite a few frameworks focused on agent memory now, and I\u2019m not sure if yours is better than Mem0.","title":null,"type":"comment","url":null},{"author":"Junnn","children":[],"created_at":"2026-01-06T13:07:17.000Z","created_at_i":1767704837,"id":46511750,"options":[],"parent_id":46511540,"points":null,"story_id":46511540,"text":"I\u2019m working on a sales assistant agent with long-term memory. What database does memU support by default? I\u2019m using pg.","title":null,"type":"comment","url":null},{"author":"quinncom","children":[],"created_at":"2026-01-06T17:56:20.000Z","created_at_i":1767722180,"id":46515886,"options":[],"parent_id":46511540,"points":null,"story_id":46511540,"text":"It appears that this is a tool useful for people who are building AI agents. Rather than for people who are using AI agents such as Claude Code. MCP is not mentioned in the README.","title":null,"type":"comment","url":null}],"created_at":"2026-01-06T12:43:39.000Z","created_at_i":1767703419,"id":46511540,"options":[],"parent_id":null,"points":11,"story_id":46511540,"text":"Hi HN,<p>We\u2019ve been building [memU](<a href=\"https:&#x2F;&#x2F;github.com&#x2F;NevaMind-AI&#x2F;memU\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;NevaMind-AI&#x2F;memU</a>), an open-source memory framework for AI agents that supports both classic RAG and LLM-based direct file reading.<p>RAG has become the default in LLM systems, but many of its failures don\u2019t come from the model \u2014 they come from the retrieval assumptions. Embedding-based retrieval is fundamentally an approximation over semantic similarity. It works well for fuzzy recall, but it often breaks when <i>relevance \u2260 correctness</i>, which is common in real systems.<p>From a retrieval perspective, RAG struggles with:\n- Time- and version-sensitive facts (embeddings don\u2019t encode validity or order)\n- Structured, canonical knowledge like configs, policies, or agent state\n- Multi-step reasoning, where incomplete or slightly wrong context compounds errors<p>In practice, RAG often returns plausible but incorrect context \u2014 especially harmful for agents that act over long horizons.<p>memU takes a different approach.<p>Instead of trying to make embedding search smarter, we ask: <i>what should not be retrieved via embeddings at all?</i><p>Retrieval in memU starts at a Memory Category Layer:\n- memory is organized into semantically stable categories\n- each category is stored as a readable Markdown file\n- these files act as long-term, canonical memory<p>When a query arrives, the LLM reads the relevant memory files directly, using semantic understanding rather than vector similarity. Only when this layer is insufficient does memU fall back to item-level retrieval, optionally using embeddings for speed.<p>This design treats the LLM as what it\u2019s increasingly good at: reading, reasoning, and maintaining structured knowledge, not just ranking vectors. Using Markdown files is deliberate \u2014 similar to ideas like `skills.md` \u2014 making memory explicit, inspectable, and stable over time.<p>Compared to existing approaches:\n- [mem0](<a href=\"https:&#x2F;&#x2F;github.com&#x2F;mem0ai&#x2F;mem0\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;mem0ai&#x2F;mem0</a>) is fast and simple with classic RAG, but can struggle with temporal accuracy and precise state changes.<p>- [Zep](<a href=\"https:&#x2F;&#x2F;github.com&#x2F;getzep&#x2F;graphiti\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;getzep&#x2F;graphiti</a>) uses graphs, which handle structure well but add complexity and maintenance overhead.<p>- [memU](<a href=\"https:&#x2F;&#x2F;github.com&#x2F;NevaMind-AI&#x2F;memU\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;NevaMind-AI&#x2F;memU</a>) uses non-embedding retrieval to address RAG\u2019s structural limits in accuracy, stability, and long-term consistency \u2014 without replacing RAG entirely.<p>For long-running agents, retrieval needs to provide reliable premises for reasoning, not just relevant text. In those settings, direct LLM reading over structured memory often aligns better with how models actually reason.","title":"Show HN: A file-based agent memory framework that works like skill","type":"story","url":"https://github.com/NevaMind-AI/memU"}
