Vouch and maintainer guidance: Mnemosyne memory backend

[wannfq]

Hey! I use mnemosyne-oss/mnemosyne and would love to use the same local memory from OMP too. I opened #6243 with an idea for making it a proper OMP memory backend, so OMP can recall useful context, save it, and use it during compaction—not just expose a few MCP tools.

I am happy to put together a PR. Before I start, does that sound like something maintainers would want? If so, I would love a little direction on the backend name, how OMP should connect to Mnemosyne, and what to keep in the first version.

I saw that vouches are temporarily optional in the contribution guide. If they are still helpful for a change like this, I would really appreciate one.

I might also start a Discord discussion before I begin building it.

Issue: #6243

[TomLucidor]

Compare this to ALL other major memory modules (>50 stars), and how is this better than the rest (or at the very least the most applicable)?

[wannfq]

Because this is the most popular local-first, agent-agnostic memory system. This is the very engine that power OMP mnemopi. But, I don't think there's interportability of the database between mnemopi and mnemosyne.

Happy to be corrected.

[MMcollab-dotcom]

How good is mnemosyne?