Hermes Agent vs MemPalace

Hermes Agent is NousResearch's open-source AI assistant built around a closed-loop learning architecture — the agent doesn't just execute tasks, it synthesizes new skills from complex interactions, self-improves those skills during use, and maintains a deepening model of the user across sessions. With 115,000+ GitHub stars, it has become one of the most-adopted autonomous agent projects in the open-source ecosystem. The system runs on 200+ models via OpenRouter, Nous Portal, NVIDIA NIM, and others, with tool-based provider switching that requires zero code changes. Users can interact via a terminal interface or through Telegram, Discord, Slack, WhatsApp, or Signal — all from a single gateway process. Built-in cron scheduling enables fully unattended workflows, and the agent can spawn isolated subagents for parallel workstreams. What sets Hermes apart from typical agent frameworks is the memory layer: it captures observations via five session hooks, stores them in SQLite with FTS5 search, and uses a Chroma vector database for semantic retrieval — cutting context costs by ~10x versus naive approaches. The result is an agent that genuinely accumulates expertise over time rather than starting from scratch each session.

MemPalace is a free, MIT-licensed AI memory framework that stores LLM conversation data verbatim locally — no AI summarization step, no per-query API costs. It integrates with Claude Code, ChatGPT, and Cursor via MCP, and claims the highest LongMemEval benchmark score among free memory frameworks at 96.6% (initially claimed 100% before community pressure forced a correction after GitHub issue #29 exposed test-set tuning). The project went viral on GitHub with 23,000+ stars in under 48 hours, partly because it was built by actress Milla Jovovich and developer Ben Sigman — an unusual origin story that dominated early coverage. But the technical pitch is real: competing paid solutions (Mem0 at $19–249/month, Zep at $25+/month) do similar things and charge for the privilege. MemPalace runs fully local, connects to any POSIX filesystem, and the verbatim storage approach avoids hallucination artifacts introduced by AI-summarized memory. The catch: verbatim storage means much higher storage overhead than summarization-based approaches, retrieval latency grows with context size, and the benchmark controversy raised questions about the team's methodology. For personal projects and small teams, the zero-cost angle is hard to argue with. For production systems where memory quality is critical, wait for independent benchmarking.