
Why I'm Asking for Help
I've been out of work for nine months. Our savings are gone. We're behind on rent and facing eviction. If Mnemosyne has ever helped you, please read this.
Updates, Geschichten und Gedanken zum Bau von Speichersystemen, die Ihre Privatsphäre wirklich respektieren.

I've been out of work for nine months. Our savings are gone. We're behind on rent and facing eviction. If Mnemosyne has ever helped you, please read this.
Cross-agent shared memory, multilingual MEMORIA for German/Russian/Chinese, custom embedding endpoints, and 21 bug fixes. v3.0 was the foundation. v3.1 is the expansion.
Kevin Simback published a deep guide on Hermes memory systems and put Mnemosyne in Layer 3 alongside GBrain as one of two standout community projects.
From 35.4% to 65.2% on BEAM, leading published SOTA. Multi-hop reasoning went from 16.7% to 87.5%. Same zero-cloud architecture. MEMORIA changed everything.

Mnemosyne started as a side project. Now it has a home. Come hang out with people who believe your AI's memory should live on your machine, not someone else's server.
Three new features shipped: tiered degradation that keeps memories for years without manual pruning, entity-aware compression, and a veracity signal so you know which memories to trust.
A hallucinated dashboard, a decision matrix, and the contamination discovery that changed everything. The real story of how Mnemosyne v2.3 got tiered memory degradation, smart compression, and a confidence signal for every memory.
v2.3 just shipped. The docs are honest. The comparisons are real. Here's what comes next: expanding beyond Hermes, staying local-first, and navigating the cloud question the community raised.
A local-first web dashboard for browsing, visualizing, and understanding your AI memory. No cloud calls, no external deps, just you and your data. Built on top of Mnemosyne by wysie.
Twenty-four days, eight phases, and one stubborn belief: your AI's memory should live on your machine, not someone else's server. Here's what 2.0 brings.
Eight phases of rebuilding. What broke, what worked, and why it took 24 days.
The struggle to integrate with Hermes Agent. The directory mismatch bug. The register() export saga. Why plugin systems are harder than they look.
Moving from simple recall to four memory types. The insight that not all memories are equal. sqlite-vec, FTS5, and the first consolidation.
The first commit. Why build yet another memory system? The frustration with cloud lock-in. The decision to use SQLite. The first 24 hours of coding.