Memory for openclaw
Hi everyone. I've actually been struggling quite a bit thinking about memory for openclaw and would really like to hear your opinions and setups.
I've already watched a ton of YouTube videos, checked out many repositories, even half-hacked the codex to make it write to me about candidates for memory slots for a plugin or just memory. But YouTube videos are full of fluff and ads, so they don't really reveal how memory actually works. I'd like to discuss specifically how it works for you.
Right now I'm using a standard memory-core with hybrid search and extra paths, backend builtin. For me, this is convenient — I don't need to store any company documentation or turn the assistant into a database. It's enough for me that it remembers our daily notes. I also added extra paths with a few important .md files.
I'd like to hear what you're using? I looked into the QMD backend, but as I understand it works exclusively with local embeddings and a local reranker, which I really wouldn't want to install. I'm fine with just embeddings from OpenRouter.
Please tell me who uses what — maybe there are QMD, gbrain, lancedb, lancedb-pro, or cognee users here?
Let me say right away — I'm not talking about contextengine (like lossless-claw), but specifically about memory.
Ideally for me, it's transparency of notes and session support. It seems like with the built-in backend you can connect not only extra paths but also session transcripts, but I don't know if that will work or just pollute the search. Are there people here who have enabled session transcription via the built-in search engine?