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 the latter approach to work much, much better than simple “store”/“remember” systems.

So, it just feels misleading to say this can do what Claude.ai’s can do…

(I’ve been looking for a memory system that works the same for a while, so that I can switch away from Claude.ai to something else like LibreChat, but I just haven’t found any. Might be the only thing keeping me on Claude at this point.)

-

*I say Claude.ai because that’s specifically what has the system; Claude Code doesn’t have this system

• flippyhead

  today at 12:52 PM

  I really want to try this approach. I'm curious because this has not been my experience at all. I created https://github.com/flippyhead/ai-brain mostly just for myself and a few friends use it. But so far, telling the AI (via CLAUDE.md) to look for relevant memories and to think about when and how to save them has worked very well. It can create structures based on decided priorities, notes for the future, that feel like they'd be very different if it was just trying to summarize everything.

• kuboble

  today at 12:36 PM

  That's an interesting concept. So it's like if you're an agent chatting with a user, you have an army of assistants who overhear the conversation and record important facts, or search relevant facts on some database and decide on the fly when to interrupt you with "this memory X looks relevant". Sounds easy enough if tokens were free, but an interesting problem to do it efficiently.

• kimjune01

  today at 12:20 PM

  I agree. silent agent doing agentic things async is what would be helpful, not requiring a modification to the main prompt

  • aprilnya

    today at 12:24 PM

    Yeah. The other advantage is a summary-based memory also just… “pieces together” things that a “store”/“remember” memory wouldn’t, because they’re things that the actual main agent would not think to store. i.e. small disconnected things across conversations that alone, would not end up in memory because they’re insignificant. But when there’s an agent looking at multiple conversations at once it can actually reason about this stuff and piece it together.

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 yourself? That sort of thing.

Not casting aspersions on you personally, I’d really like this from every project, and would do the same myself.

• dennisy

  today at 9:38 AM

  This is a fair question, but not one I feel we can let people self answer.

  I doubt many people will honestly admit they did no design, testing and that they believe the code is sub par.

  It does give me an idea that maybe we need a third party system which can try and answer some of the questions you are asking… of course it too would be LLM driven and quite subjective.

  • embedding-shape

    today at 10:51 AM

    > I doubt many people will honestly admit they did no design, testing and that they believe the code is sub par

    I'd doubt any engineer that doesn't call most of their own code subpar after a week or two after looking back. "Hacking" also famously involves little design or (automated) testing too, so sharing something like that doesn't mean much, unless you're trying to launch a business, but I see no evidence of that for this project.

  • dwb

    today at 10:32 AM

    > I doubt many people will honestly admit they did no design, testing and that they believe the code is sub par.

    Well no, but if people want to see a statement like this, and given that most people will want to be at least halfway honest and not admit to slop, maybe it will help nudge things in the right direction.

• codebolt

  today at 11:17 AM

  There are many ways to use an LLM to generate a piece of software. I base most of my projects these days around sets of Markdown files where I use AI first to research, then plan and finally track the progress of implementation (which I do step-wise with the plan, always reviewing as I go along). If I was asked to provide documentation for my workflow those files would be it. My code is 99% generated, but I take care to ensure the LLM generates it in a way that I am happy with. I'd argue the result is often better than what I'd have managed on my own.

  • dwb

    today at 12:15 PM

    Yep pretty much same, although if I’m lax at any point of the reviewing (in-progress or final), I’d say the quality quickly drops to below my average manual effort, and then I don’t even have the benefit of thinking it all through as directly. I think getting really quality results out of LLM code generation for non-trivial projects still needs quite a bit of discipline and work.

• chickensong

  today at 10:58 AM

  What's the point? You can make good or bad software, with or without LLMs. Do you ask a carpenter if they use a hammer or nail gun? Did they only use the nail gun for the roof and the deck?

  If you care that much and don't have a foundation of trust, you need to either verify the construction is good, or build it yourself. Anything else is just wishful thinking.

  • hirako2000

    today at 11:20 AM

    We do ask whether it's handmade or factory.

    We even ask when cakes are made in house or frozen even though they look and taste great (at first).

  • dwb

    today at 12:16 PM

    It’s not all-or-nothing: a statement like what I want would be part of the assurance, not the whole thing.

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?

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.

• hirako2000

  today at 11:34 AM

  It's a cool website..it says memory. It shows LLM suck and this product magically just works.

  In a way, if it does accomplish that, it is a vectordb needing glorification.

A few things seem to work well for me (Codex):

1) An up-to-date detailed functional specification.

2) A codebase structured and organized in multiple projects.

3) Well documented code including good naming conventions; each class, variable or function name should clearly state what its purpose is, no matter how long and silly the name is. These naming conventions are part of a coding guidelines section in Agent.md.

My functional specification acts as the Project.md for the agent.

Then before each agentic code review I create a tree of my project directory and I merged it with the codebase into one single file, and add the timestamp to the file name. This last bit seems to matter to avoid the LLM to refer to older versions and it’s also useful to do quick diffs without sending the agent to git.

So far this simple workflow has been working very well in a fairly large and complex codebase.

Not very efficient tokens wise, but it just works.

By the way I don’t need to merge the entire codebase every time, I may decide to leave projects out because I consider them done and tested or irrelevant to the area I want to be working on.

However I do include them in the printed directory tree so the agent at least knows about them and could request seeing a particular file if it needs to.

• swingboy

  today at 11:21 AM

  Interesting approach. How do you do the merging? Is it manual? Just changed files? A hybrid?

It's not clear to me how or why this works, and how it compares to just using md files in my project. For something like this, we really need benchmarks.

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 area.

The only approach I've found that works is no memory, and manually choosing the context that matters for a given agent session/prompt.

• jvwww

  today at 9:59 AM

  Yeah I feel the same way. Wonder when/if we'll get continual learning from these models. I feel like they are smart enough already but their lack of real memory makes them a pain to deal with.

  • hirako2000

    today at 11:37 AM

    Google Gemini does this sort of thing. External to the model k presume. And it's very annoying.

    A friend told me he would like Claude to remember his personality, which is exactly what Gemini is trying to do.

    A machine pretending to be human is disturbing enough. A machine pretending to understand you will spiral very far into spitting out exactly what we want to read.

• clutter55561

  today at 9:34 AM

  All the memories Claude created for me fell in the category remember-to-not-forget, so I disabled it altogether.

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.

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

• dennisy

  today at 7:45 AM

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

  • awestroke

    today at 9:42 AM

    Well let's talk again when the problems have been solved, then. Until then, manually curated skills and documentation will beat this

• vasco

  today at 8:15 AM

  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"

this is a patch on top of the broken flat-compaction caching algorithm used by coding agents. Why not fix the cache algorithm directly? Union-find is a better impl june.kim/union-find-compaction

>Stash makes your AI remember you. Every session. Forever.

How does it fight context pollution?

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.

is this backed by a hollywood celebrity ?

Congratulations on the launch!

There is lots of competition in this space, how is your tool different?

Wow another day, another memory system for AI agents!

How many are we up to now? Has to be hundreds of them.

• dominotw

  today at 12:38 PM

  its the todomvc of ai user. i made one for myself too. I try not to tell anyone about it .

Platform memory is locked to one model and one company. Stash brings the same capability to any agent — local, cloud, or custom. MCP server, 28 tools, background consolidation, Apache 2.0.

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.

There is already memory palace ?