Over time, I can imagine there's going to be a lot of sensitive information being stored. How are you handling privacy?
We already support the feature of inclusion and exclusion of memories where the developer can control what things to remember vs not remember for their AI app/agent. For example, you can specify something like this: - Inclusion prompt: User's travel preferences and food choices - Exclusion prompt: Credit card details, passport number, SSN etc. Although we definitely think that there is scope to make it better and we…
Show HN: Mem0 – open-source Memory Layer for AI apps
61–70 of 73 posts
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#62Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#63(I hope it's ok to share something I've built along a similar vein here.)
I wanted to get long-term memory with Claude, and as different tools excel at different use cases, I wanted to share this memory across the different tools.
So I created MemoryPlugin (https://www.memoryplugin.com). It's a very simple tool that provides your AI tools with a list of memories, and instructs them on how to add new memories. It's available as a Chrome extension that works with ChatGPT, Claude, Gemini, and LibreChat, a Custom GPT for ChatGPT on mobile, and a plugin for TypingMind. Think of it as the ChatGPT memory feature, but for all your AI tools, and your memories aren't locked into any one tool but shared across all of them.
This is meant for end-users instead of developers looking to add long-term memory to their own apps.
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#64Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#65Great product, thanks for releasing it for the opensource community. Have you considered replacing Neo4j with something more cost-effective like Memgraph?
When I worked as a consultant in the knowledge graph area I ran into clients over and over against who had failed with Neo4J, which I'd never done because I read the Neo4J manual and understood it just wasn't an industrial strength tool.
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#66Looks nice. Would the open-source version work from within an Electron app used for local LLM chats? I.e. can I run the memory management, retrieval, and database locally in javascript? I believe the answer is "no, you can only run the memory management code in Python, the javascript code is only a client SDK for interacting with the managed solution". In which case, no worries, still looks awesome!
Disclaimer: I built it.
Context: We are using mem0 in another open-source project of ours (Typescript) and had the same questions. So we went ahead and built a small api server for ourselves.
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#67Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#68Hi this looks interesting. From your description it looks like mem0 remembers details and context of previous chats but not the actual text of chats. Is this a correct assumption?
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#69Hi this looks interesting. From your description it looks like mem0 remembers details and context of previous chats but not the actual text of chats. Is this a correct assumption?
Hey, yes. It remembers whatever is important from the previous chats.
==== Bot: wassup?
Me: I have some more thoughts on Project X. They will be rambly so please also create an edited version as well as the usual synopsis. I will say 'I'm finished' when I've finished.
Bot: ok hit me
Me: bla bla bla bla etc etc. I'm finished.
Bot: this looks like part of the introduction text of Project X, is that correct?
Me: yes. What meta tags do you suggest? Etc ====
I'm assuming that a custom GPT or equivalent is necessary to set out the 'terms of engagement' and agent objectives. Can you offer any advice about building such a system, and how mem0 could help?
Re: Show HN: Mem0 – open-source Memory Layer for AI apps
#70why a graph db, can you please illustrate how it helps
It's a very similar reason on why using Graph for RAG can help you get much more accurate responses than with Vector RAG. See a blog I wrote about it https://www.falkordb.com/blog/knowledge-graph-vs-vector-data...