supermemory

hey many of you don't know what we actually do at @supermemory, so here's a short intro: TL;DR is: if you're thinking about memory / context in any way, you should use supermemory. - we are a team obsessed on building the best memory and continual learning system - we primarily sell to companies building agents. Today we serve many thousands of companies (and tens of millions of users that they cater to) - supermemory is very scalable and people use us because we're at the pareto of being good quality + being the most affordable way to do memory. - you can also run supermemory fully locally, host it on your premise, or VPC (talk to us) xitter.twitterapi.xyz/supermemory/status/206… - you can also use supermemory for knowledgebases and retrieval, and we're better and cheaper on that front too. xitter.twitterapi.xyz/supermemory/status/210… - you can use supermemory with your own personal agents too (claude code, openclaw, etc.) - we have a free plan so you can use it on your note taking sideproject :) - it is that cheap and fast because we build the infra ourselves -- our own database primitive, and a model that is really good at long horizon learning - it is different to other memory systems because we also think a lot about harness/product side. We're the only ones with hooks + tools approach, a user profile is created for everyone and injected into the model with hooks. - you can tune everything about supermemory. you can customize it. - think of it as a living, breathing database. xitter.twitterapi.xyz/supermemory/status/211… - but in reality, it's kinda like a graph xitter.twitterapi.xyz/supermemory/status/211… - our database can also be represented as a filesystem. xitter.twitterapi.xyz/DhravyaShah/status/206… - i have been working and thinking about this for 4 years now. the memory benchmarks are not very telling of what people need in the real world. I've spoken to 10,000+ people building in this space. a lot of things about supermemory's product are built with extreme care xitter.twitterapi.xyz/supermemory/status/210… - the infra: is really scalable. we have dreaming etc. which dynamically decides when and how to process information xitter.twitterapi.xyz/supermemory/status/210… - one more reason it's really cheap is because of a really banger model we built that is cheap but better than frontier xitter.twitterapi.xyz/supermemory/status/209… TL;DR: you should just use supermemory. xitter.twitterapi.xyz/supermemory/status/208…

Conversation with @DhravyaShah, Founder of SuperMemory 00:00 Cloudflare Culture & Working Under CTO 01:36 Autonomy, Writing Culture & Product Flywheel 02:45 Product Life Cycle: Idea to Launch 04:28 Demo Days & Engineering Writing Culture 06:32 Origins of Supermemory 08:00 Acquiring the Domain 08:59 Going Viral on GitHub & VC Interest 10:03 Turning Down Early Investment Deals 13:38 Early Investors & Susa Ventures 17:08 Shifting from Product to Infrastructure 18:49 The Market Street Epiphany & Shutting Down Products 22:04 Focusing on AI Memory & Continuous Learning 24:47 Inbound Go-to-Market Strategy 27:28 Testing Memory via AI Companions 28:11 AI Companion Dynamics & Psychosis Risks 30:31 Embracing Iteration Velocity 31:31 Lessons from Company Brain 33:25 Defining Good Memory Systems 34:32 Rethinking Memory Retrieval & Injection 36:45 Supermemory Architecture & Local Models 39:00 Memory for Continual Improvement 41:33 Agent-to-Agent Security Risks 43:32 Public Identity & Personal Growth 46:12 Productivity Philosophy

Introducing MemoryRepo.dev. an open source implementation of Cognition's dreaming memory system, same as Instinct, Muse, Openclaw, etc., built on @cloudflare Artifacts, Durable objects, Alchemy and Effect. I've been exploring agent memory for a long time and this is one of the more popular ways to do it, and I'm happy to see cognition putting out a detailed spec of how they perceive this. In a way, it's beautifully simple and encapsulates what a good memory system should have. There's many pros and cons, here's a video of me talking about it ↓ If you're thinking about agent memory you should probably use @supermemory - we think a lot about the very specific details about all of this. But, if you're curious, github.com/supermemoryai/mem… is a great place to start with the cognition memory thing as well. we're actually going to incorporate some of the learnings from the research we're doing here into supermemory (soon-ish). but open sourcing it for public benefit :) sorry for the bad audio quality, did it as a quick thing