Viktor.comAn AI coworker that actually does the work
Memdex
Turn every AI conversation into reusable local memory
498 followers
Turn every AI conversation into reusable local memory
498 followers
Memdex is a Chrome extension that turns every AI conversation into reusable memory. It auto-captures your chats across ChatGPT, Claude, and Gemini, stores them encrypted on your laptop (IndexedDB, never uploaded), and underlines reusable context in your next prompt like Grammarly underlines typos. One click to inject when you need it just like grammarly. Free for your 10 most recent chats. Pro for unlimited.
Mapify
@xeasonchan I use Claude with a browser automation extension to handle long tasks. The problem is the context window fills up mid-task, and I have to star a new conversation — but the job isn't done yet. Every time I restart, I have to re-explaiin everything from scratch: what I was doing, how far I got, what's next.
Does Memdex handle this kind of scenario? Can it capture and resume that kind of task context, not just regular chat conversations?
@dora_lin2 Hi, I can relate to your problem of re-explaining context do you still face it or have found any solution?
Mapify
@xeasonchan "never uploaded" and "injected into Claude on every relevant prompt" are both on your page, and both true. that's the part I'd want addressed head-on, Andrew.
the memory rests on my machine, sure. but the second it's useful, it travels into someone else's model. local-first storage, cloud-first exposure.
do users get to mark certain memories as never-inject? the work-stuff-yes, the therapy-session-no kind of split? feels like that toggle is what separates "encrypted on disk" from actually private.
congrats on the launch either way, this is a real problem worth getting right.
Wingbits AI
@xeasonchan Love the idea of cross-model memory. One thing I’m curious about: how are you handling relevance detection locally without turning into “prompt bloat”? Like, what signals decide which past chats get injected vs ignored?
@xeasonchan I use claude pro and store all my files in a project and have conversations using those project repositories. The issue i face is sometimes chat conversations get long and once it exceeds a limit, claude asks to open a new chat . When I open a new chat, I got to ask it to summarize previous chat information and use it back and it doesn't fully recognise the conversation style or the details to full extent. Does this address the scenario?
The Grammarly-for-context framing is strong. The place I’d be careful is separating durable memory from stale task state.
Some things really should follow me everywhere: product constraints, preferred wording, customer language, recurring project facts. Other things are only useful for this week’s thread and become confusing later. I’d love a lightweight way to mark injected context as “keep reusing this” vs “only for this task/session,” plus a small preview of why Memdex thinks a prior chat is relevant before it inserts it.
@jim_jeffers Good question, I was wondering the same thing. The "keep this forever" vs "only for this task" distinction is exactly the kind of UX detail that makes or breaks a memory tool long-term. Curious if the maker will chime in on this — a simple tagging or expiry mechanism would go a long way.
Mapify
That makes sense. The part I’d keep making visible is the “why this section, not the rest?” decision.
If the user can see a small injection preview — project memory, last touched date, 3 snippets selected, 40 other notes ignored — they can trust the context without reading an audit log. It also gives them a chance to catch the dangerous case where old context is technically relevant but no longer true.
I just woke up and opened Product Hunt to see what’s launching today. Memdex caught my eye so I went through the homepage, and the way you described the context detection flow felt clean. Great work! By the way I lose my best AI chats all the time. Scrolling through the history is a nightmare. So this idea... I like it. I have a question though. Since everything stays on my device, how does the matching actually work? Is it just looking for the same words, or does it understand the meaning behind them? Either way, cool product. Rooting for you.
Mapify
@xeasonchan Thank you for the detailed response. So it learns my style over time. That's smart. I will keep an eye on how this grows. One more thing... do you have a LinkedIn page or Twitter for Memdex?
Mapify
"Reusable local memory" is the part most AI tools paper over with "your data is private" wording without actually solving the locality problem. Curious which decision was harder — the storage shape or deciding what NOT to capture. That second one usually defines how a memory tool ages.
Mapify
Mapify
First of all congrats on your launch!
I just checked your website and landing page storytelling is great which is usually first thing that caught my eye in any new tool and something i spent good time to deliver it in my own tool as it is the first impression for any new user.
I use Claude a lot and many times it misses the past convos even though i ask it to update the memory but in fact it still repeats the same old information. Does Memdex helps solving this issue?
Mapify