Hi 👋 Apparently this place exists, and I should've found it 14 months ago
Confession: I've been weekend-warrioring on memset.io for over a year and only learned Indie Hackers was a thing yesterday. Posted about my project on LinkedIn expecting five likes from coworkers, a few people told me I should be on IH. So... here I am.
The short version: my Nana passed, I started building something in her memory, then my computer crashed and I realized... code was safe on GitHub, but everything I'd learned solving problems with AI was gone. So I built a memory layer that follows me across ChatGPT, Claude, Cursor, Gemini, all of them.
Free tier, paid tier mostly exists to stop one specific friend from melting my Cursor/Claude bill.
I genuinely have no idea what people do here besides post their products. What's worth my time as a solo weekend builder? Mostly here to learn from folks who've done this longer than me.
The context loss thing is real though, I've had Claude forget entire project setups mid-conversation and had to start over.
How does it sync across tools? Does it inject context automatically when you open a new chat or do you have to manually pull it in each time?
Great question Muhammad. Currently I have it as passive injection - i.e. the system detects what you're talking about and if a relevant memory exists within your brain it pushes that memory as an option to you; you can then decide if you want to inject that memory or if you don't want to.
Note that this only works if you're actively engaged with a system (Claude, Cursor, ChatGPT etc..). For your example, where you open a new chat, and the system has no context about what you may or may not want to investigate/explore.. you would force recollection using the /recall command.
That passive injection approach is smart — less intrusive than forcing context every time. The /recall command makes sense for cold starts too.
Curious: does it work across browsers or is there an extension involved? Will give it a proper try this week.
Currently the ecosystem that feeds the brain consists of:
- Chrome Extension
- MCP
- CLI
So, it won't work across browsers.
However, I am in the final stages of building a desktop client and going through the update approvals across Windows/MAC. The desktop client would cover all surfaces on a desktop; and then I'll build out a mobile app as well.
Is a roadmap with all the future state stuff I'm piecing together on the roadmap linked off the home page.
Moving to a desktop client is a massive upgrade because it takes the "brain" out of the browser silo and makes it universal across every coding environment you have open. Eliminating that browser-only limitation means the AI can actually stay synced whether you're in a terminal, a specific IDE, or just drafting documentation. By the way, I work in PR and media placement for deep-tech and productivity tools, and this vision of a "cross-surface" AI memory is a really high-authority story that would land well with major tech news outlets.
Always down to talk more about the solution and get more eyes on it. Feel free to reach out to me directly Muhammad, email is just keith@ the web url.
Just sent you an email, Keith! Looking forward to hearing more about the roadmap. Cheers!