Live data from Hacker News

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

alash3al.github.io

1–10 of 87 posts

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

#3
LLM Memeory (in general, any implementation) is good in theory.

In practice, as it grows it gets just as messy as not having it.

In the example you have on front page you say “continue working on my project”, but you’re rarely working on just one project, you might want to have 5 or 10 in memory, each one made sense to have at the time.

So now you still have to say, “continue working on the sass project”, sure there’s some context around details, but you pay for it by filling up your llm context , and doing extra mcp calls

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

#5

LLM Memeory (in general, any implementation) is good in theory. In practice, as it grows it gets just as messy as not having it. In the example you have on front page you say “continue working on my project”, but you’re rarely working on just one project, you might want to have 5 or 10 in memory, each one made sense to have at the time. So now you still have to say, “continue working on the sass project”, sure there’…

True! But this is a very naive implementation, a proper implementation could surpass these challenges.

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

#6
Well the project is promising something without providing any details how exactly this is achieved which to me is always a huge red flag.

Digging deeper I can see it is effectively pg_vector plus mcp with two functions: "recall" and "remember".

It is effectively a RAG.

You can make the argument that perhaps the data structure matters but all of these "memory" systems effectively do the same and none of them have so far proven that retrieval is improved compared to baseline vector db search.

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

#7

LLM Memeory (in general, any implementation) is good in theory. In practice, as it grows it gets just as messy as not having it. In the example you have on front page you say “continue working on my project”, but you’re rarely working on just one project, you might want to have 5 or 10 in memory, each one made sense to have at the time. So now you still have to say, “continue working on the sass project”, sure there’…

And once you're being specific about what it needs to remember you are 0 steps away from having just told AI to write and read files with the "memory"

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

#8
Isn’t “memory” just another markdown file that the LLM reads when starting a new session?

I keep two files in each project - AGENTS (generic) and PROJECT (duh). All the “memory” is manually curated in PROJECT, no messy consolidation, no Russian roulette.

I do understand that this is different because the vector search and selective unstash, but the messy consolidation risk remains.

Also not sure about tools that further detach us from the driver seat. To me, this seems to encourage vibe coding instead of engineering-plus-execution.

Not a criticism on the product itself, just rambling.

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

#9
Is this only for vibecoders who work alone?

If I am working on a real project with real people, it won’t have the complete memory of the project. I won’t have the complete memory. My memory will be outdated when other PRs are merged. I only care about my tickets.

I am starting to think this is not meant for that kind of work.

Post reply on HN