Hermes Agent vs qmd

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.

qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.