Comment by gdad

Building in the same space (Maximem Vity, cross-LLM memory as a Chrome extension and OpenClaw plugin). The SMTP analogy really resonates with me. I wrote a comparison a few weeks ago of how ChatGPT, Claude, and OpenClaw actually implement memory under the hood [1] and the architectures are so different that interop feels almost accidental when it works. One thing I keep running into: the hard part isn't storage or retrieval. It's qualification. Deciding what's worth remembering from a conversation vs. what's throwaway context. ChatGPT takes the "summarize the last 15 chats" approach, Claude does on-demand search, and both have real failure modes. We went with a semantic graph that tries to capture relationships between memories (your preference for serverless connects to your AWS project connects to your cost constraints) rather than flat key-value pairs. Still iterating on it honestly. Re: Claude's import-memory launch yesterday, I think the timing validates the category but the approach is fundamentally migration, not sync. You import once, and from that moment your contexts diverge again. Anyone using 3+ tools daily (which is basically everyone I talk to) is back to fragmented memory within a week. Curious about your retrieval approach. Are you doing hybrid search or pure semantic? [1] https://www.maximem.ai/blog/ai-apps-memory