Live data from Hacker News

Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

alash3al.github.io

61–70 of 87 posts

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#61

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

Just write a hook that runs claude -p after whatever you want and update whatever memory system you want. You can use a channel to inject back what topics were update or what have you.

I am not sure how using Claude -p is going to help you imitate Claude’s memory system for any ai agent…

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#62

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

How do you benchmark that? The problem with extracting memories in the background is it's hard to make that work with the prefix cache. You can go a long way with a simple 2-stage LOG.md (detailed log of tasks & lessons) + MEMORY.md (log items that are promoted when the log itself gets truncated) + a stop hook to ensure this runs at the end of a turn.

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#63
post #11

I’m certainly on the lookout for something like this and I’m happy to see your account has published software from before the LLM boom as well. I guess I’d like some kind of LLM-use-statement attached to projects: did you use an LLM to generate this, and if so, how much and what stages (design, build, test)? How carefully did you review the output? Do you feel the quality is at least what you could have produced by y…

I’m sorry this sounds a bit too entitled - no one is putting a gun to your head to use this project and you know you can always read the code and review it yourself and make an educated decision on whether you want to use it or not

Weird. The project is obviously holding itself out to be some amazing awesome new thing. Extraordinary claims at least invite questions like this.

Or are you all suggesting we should be comfortable with, and never question, flowery unchallenged advertising copy?

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#64

I still haven't found useful "memory". It's either an agents.md with a high level summary, which is fairly useless for specific details (eg "editing this element needs to mark this other element as a draft") or something detailed and explaining the nitty gritty, which seems to give too much detail such that it gets ignored, or detail from one functional area contaminates the intended changes in another functional are…

[dead]

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#65
post #27

What the heck is happening on this site with the pointer disappearing? For some reason the body tag has "cursor: none" which is never good.

I didn't read much of the page - just was scrolling a bit to see what the fuck that thing is doing, and that was more than enough to know that I'll never touch whatever those people are doing.

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#66

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

Just write a hook that runs claude -p after whatever you want and update whatever memory system you want. You can use a channel to inject back what topics were update or what have you.

Sure, but the idea is not to have this in Claude Code, the idea is to be able to use something like LibreChat with proper memory. I don’t really need that good of a memory system for my coding agent, it’s definitely more something I need for my chat agent.

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#67

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

In the recent Claude Code leak, there was apparently something called "autoDream", a "background memory consolidation engine" according to this: https://kuber.studio/blog/AI/Claude-Code's-Entire-Source-Cod...

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#68
Now that building software is effectively free, it's astounding that we're still trying to pitch things like this using a vibe-coded fancy marketing site. Who has time to use these and wait weeks or months to find out if they actually work? There's no proof in the site this is better than RAG or even a folder of memory files and grep, yet makes all these fantastic claims (while scrolling at 14fps). This wasn't even coded 24 hours ago... It's honestly so lazy.

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#69

All these agent memory systems seem so simultaneously over and under engineered and like a certain dead end. I cannot imagine any reality in which this does not rot and get out of sync with what the latest model need. For the one time you build a payment provider how many session will be tilted towards thinking about payments because of the "don't use stripe" memory?

What's worse is how obvious the author hasn't even used it themselves. Completely unproven memory layer. No due diligence - just a fancy marketing site with outrageous claims

Re: Open source memory layer so any AI agent can do what Claude.ai and ChatGPT do

#70

I clicked this thinking “oh, cool, someone finally made a portable version of the Claude.ai* memory system!” Spoiler, no, it’s not it at all, it’s just a “store”/“remember” memory system… as opposed to the Claude.ai memory system, where it doesn’t make the model actively have to write memories on its own, but rather has a model in the background go through your chat history and generate a summary from it. I’ve found…

Which is weird because if I remember correctly, there are summaries already generated by Claude on your hard drive of things you have done in the past.
Post reply on HN