Behind the idea: Why we made Dropstone remember what every other AI tool forgets
by•
We built Dropstone because we were tired of starting from zero every time we opened an AI coding tool.
Dropstone learns, remembers, and evolves with your projects — building a persistent understanding of your codebase, architecture, and workflow. It’s designed to grow with you, not reset after every session.
We’ve just launched it on Product Hunt and would love your thoughts on how memory should shape the next generation of developer tools. Your feedback will help us refine what’s coming next.
👉 Check it out here and let us know what you think!
104 views
Replies
This is a genuinely exciting direction. Most AI coding tools still behave like amnesiacs — every new session erases the context we just built. Dropstone’s idea of persistent memory directly attacks that pain point.
I’m especially interested in how you’ll handle memory governance: when the codebase changes, how does Dropstone know which memories are outdated?
Dropstone
@wang_magic1 That’s a sharp observation. We handle that with a layered memory system — semantic, procedural, and episodic. When code evolves, Dropstone compares the new state against its semantic memory graph to identify stale associations. Those outdated memories are either rewritten through active sessions or gradually decayed if no longer relevant. In short, it learns what to forget, just like it learns what to remember.
Triforce Todos
This is such a pain point! Context resets kill productivity. Excited to see how Dropstone handles long-term memory across complex repos.