How would you use the built in functionality to enable graph functionality? Metadata or another document used as the link or collection of links?
Show HN: Yet another memory system for LLMs
31–40 of 51 posts
Re: Show HN: Yet another memory system for LLMs
#32>block-level deduplication (saves 30-40% on typical codebases) How is savings of 40% on a typical codebase possible with block-level deduplication? What kind of blocks are you talking about? Blocks as in the filesystem?
Re: Show HN: Yet another memory system for LLMs
#33That sounds like a practical take on LLM memory — especially the block-level deduplication part. Most “memory” layers I’ve seen for AI are either overly complex or end up ballooning storage costs over time, so a content-addressed approach makes a lot of sense. Also curious — have you benchmarked retrieval speed compared to more traditional vector DB setups? That could be a big selling point for devs running local res…
Re: Show HN: Yet another memory system for LLMs
#34>block-level deduplication (saves 30-40% on typical codebases) How is savings of 40% on a typical codebase possible with block-level deduplication? What kind of blocks are you talking about? Blocks as in the filesystem?
I am working to improve the CLI tools to make getting this information easier but I have stored the yam repo in yams with multiple snapshots and metadata tags and I am seeing about 32% storage savings.
Re: Show HN: Yet another memory system for LLMs
#35Earlier quoted context omitted.
I am working to improve the CLI tools to make getting this information easier but I have stored the yam repo in yams with multiple snapshots and metadata tags and I am seeing about 32% storage savings.
Cool. I have no idea what "stored the yam repo in yams" means. What do you mean by "block-level deduplication"? What is a block?
Re: Show HN: Yet another memory system for LLMs
#36Re: Show HN: Yet another memory system for LLMs
#37How do you use this in your workflow? Please give some examples because it’s not clear to me what this is for.
I am also trying to stabilize PDF text extraction to improve knowledge retrieval when I want to revisit a paper I read but cannot remember which one it was. Most of these use cases come from my personal use and updates to the tool but I am trying to make it as general as possible.
Re: Show HN: Yet another memory system for LLMs
#38>MCP server (requires Boost) I see stuff like this, and I really have to wonder if people just write software with bloat for the sake of using a particular library.
Blame the committee for refusing to include basic functionality like regular expressions , networking and threads as part of the STL
Re: Show HN: Yet another memory system for LLMs
#39>MCP server (requires Boost) I see stuff like this, and I really have to wonder if people just write software with bloat for the sake of using a particular library.
The reason for depending on Boost in this repo is just few search characters away - he needs HTTP/WebSocket implementation and Boost.Beast provides it. The actual bloat here in this repo is conan.
Re: Show HN: Yet another memory system for LLMs
#40I am observing in my professional (non-Claude Max) life that context is a real limiter, from both the “too much is confusing the agent” and “I’m hitting limits doing basic shit” perspectives (looking at you, Bedrock and Github), and having a tool that will help me give an agent only what it needs would be really valuable. I could do more with the tools, spend less time trying to manually intervene, and spend less of my token budget.