s60yucca/mnemos

**The autopilot knowledge base for your coding agent.**
Install once. From then on, your agent builds itself a structured knowledge base of your project — while you code. No prompts to remember, no remember() calls, no API to learn.
Single Go binary. Embedded SQLite. Zero cloud. No Docker. No Python. No Node runtime.
---
What makes mnemos different
Every memory server stores text. Mnemos **compiles a knowledge base**.
While other servers expect you (or a carefully-tuned prompt) to decide *when* to store and *when* to retrieve, mnemos runs a full pipeline in the background:
The pipeline runs behind the MCP and hook interfaces. Agents use normal memory
tools; they do not need to orchestrate deduplication, summarization, ranking,
packing, or lifecycle maintenance themselves.
---
Three layers, all shipping today
**Layer 1 — MCP transport.** Standard MCP server, stdio, works with any MCP client.
**Layer 2 — Autopilot hooks.** One command (mnemos setup claude) wires hooks + steering + MCP config. Session start auto-injects relevant context. Prompt submit auto-searches on topic change. Session end verifies coverage.
**Layer 3 — Auto-compiled knowledge base.** Quality gate, 3-tier dedup, auto-summarization, file linking, MMR context assembly — all automatic. You never trigger them. Includes passive background daemon that continuously detects staleness, contradiction, and missing relations across your memory base.
---
Compared honestly
| | Mem0 | Zep/Graphiti | engram | OMEGA | **mnemos** |
|---|---|---|---|---|---|
| MCP-native | ✓ | ✓ | ✓ | ✓ | ✓ |
| Single binary, no runtime deps | — | — | ✓ | — | ✓ |
| Zero cloud / local-first | partial | — | ✓ | ✓ | ✓ |
| 1-command autopilot setup | — | — | — | — | **✓** |
| Auto-quality gate | — | — | — | — | **✓** |
| Auto-summarization | — | — | — | — | **✓** |
| Auto file-linking (git-aware) | — | — | — | — | **✓** |
| MMR context assembly | — | — | — | — | **✓** |
| Passive background daemon | — | — | — | — | **✓** |
| Temporal knowledge graph | — | ✓ | — | — | partial (decay + supersede) |
| Self-host cost | $0-cloud | ~$50/mo (Neo4j) | $0 | $0 | $0 |
Mnemos isn't trying to be Zep — different bet. Zep is the best answer if you need temporal reasoning over business facts and have enterprise infrastructure. Mnemos is the best answer if you're a coding agent user who wants an autopilot knowledge base that runs itself on your laptop.
---
Install
Swap claude for cursor, kiro, gemini-cli, codex, or trae. Restart your client. Autopilot runs from here.
---
What autopilot actually does
mnemos setup writes:
- **Steering file** (CLAUDE.md, .cursorrules, .kiro/steering/mnemos.md) — tells the agent what's worth storing
- **Hook config** (.claude/hooks.json or equivalent) — wires lifecycle events
- **MCP config** (.mcp.json) — registers mnemos serve as tool provider
Three hooks run automatically:
**Session start** → mnemos hook session-start
Assembles relevant memories within a token budget (MMR-diversified, file-boosted). Injects into context. Cold start (override project ID).