I’m on the other side of this - I’d like it to happen passively and in an automated fashion. Right now I’m playing around with porting concepts from zettelkasten (card based handwritten knowledge systems) to openclaw memory.

Rather than just coalescing to markdown files, the memory-zet plugin looks for actionable durable information and files it inside the existing zettelkasten system with embeddings - a quick no-LLM step (well 300m parameter query embed, it’s fast) is run against incoming chats or as a tool - this returns cards (zettels).

Zettels are somewhat unique in that the original methodology included a post-writing categorization and linking step - I have the system doing this as well. Result - cards can give you a (possibly cyclic) directed graph of connectivity. I built it for ‘centaur’ mode, so I can edit, link, unlink, move, etc through a nice little web interface.

The auto links are not the same quality I would make. But they are genuinely useful; upshot is for anything incoming, the LLM can see information directly about the query (if we have it), stuff that relates whether or not it embeds similarly, and can follow up links if they look promising with a fast tool call.

I made this memory system my daily driver yesterday; so far it is a significant improvement over the core memory extension (write to markdown files, don’t worry about compaction bro, it will be fine)!

It’s already building out people and organizational card bases for things that come in via email and whatsapp - this is a dream, basically. I think it will scale over time - but it’s at least scaling nicely over a few days of work right now.