Many commentators are, mostly fairly, criticizing the repo due to issues raised on benchmarks. This is reasonable, however many are going further to bash the repo likely due to the authors.

For me, I see a silver lining. I'll be implementing mempalace for a few small agents to have memory portability that's managed locally.

I think the benchmarker who ran independent tests in GitHub issue #39 summed it up best:

To be clear about what this all means for our own use case: we still think there's a real product here, just not the one the README is selling. The combination of a one-command ChromaDB ingest pipeline for Claude Code, ChatGPT, and Slack exports, a working semantic search index over months or years of conversation history, fully local, MIT-licensed, no API key required, and a standalone temporal knowledge graph module (knowledge_graph.py) that could be used independently of the rest of the palace machinery,is genuinely useful, and we're planning to integrate it into our Sandcastle orchestrator as a claude_history_search MCP tool exactly along those lines.

https://github.com/milla-jovovich/mempalace/issues/39