|
4 | 4 |
|
5 | 5 | # Mnemon |
6 | 6 |
|
7 | | -**Persistent memory for LLM agents.** |
| 7 | +**LLM-supervised persistent memory for AI agents.** |
8 | 8 |
|
9 | 9 | [](https://go.dev/) |
10 | 10 | [](https://github.com/mnemon-dev/mnemon/actions/workflows/ci.yml) |
|
15 | 15 |
|
16 | 16 | LLM agents forget everything between sessions. Context compaction drops critical decisions, cross-session knowledge vanishes, and long conversations push early information out of the window. |
17 | 17 |
|
18 | | -Mnemon gives your agent persistent, cross-session memory — with a single binary and one setup command. |
19 | | - |
20 | | -<p align="center"> |
21 | | - <img src="docs/diagrams/10-knowledge-graph.jpg" width="720" alt="Knowledge Graph — 87 insights connected by temporal, entity, semantic, and causal edges" /> |
22 | | - <br /> |
23 | | - <sub>A real knowledge graph built by Mnemon — 87 insights, 2150 edges across four graph types.</sub> |
24 | | -</p> |
| 18 | +Mnemon gives your agent persistent, cross-session memory — a four-graph knowledge store with intent-aware recall, importance decay, and automatic deduplication. Single binary, zero API keys, one setup command. |
25 | 19 |
|
26 | 20 | ### Why Mnemon? |
27 | 21 |
|
28 | | -Memory has a **compound interest effect** — the longer it accumulates, the greater its value. LLM engines iterate constantly, skill files cost nearly nothing to write, but memory is a private asset that grows with the user. It is the only component in the agent ecosystem worth deep investment. |
29 | | - |
30 | | -Mnemon is built on one core belief: **the LLM itself is the best orchestrator.** Rather than embedding a small LLM inside the pipeline, Mnemon lets your host LLM — the one already holding full conversation context — act as supervisor. The binary is the organ (deterministic storage, graph indexing, search, decay); the LLM is the brain (decides what to remember, how to link, when to forget). The skill file is the textbook that teaches the protocol. |
31 | | - |
32 | | -This means: **memory management logic moves from prompt to code — deterministic, testable, portable.** The same binary + skill can run on Claude Code, Cursor, or any LLM CLI that reads markdown. |
| 22 | +Most memory tools embed their own LLM inside the pipeline. Mnemon takes a different approach: **your host LLM is the supervisor.** The binary handles deterministic computation (storage, graph indexing, search, decay); the LLM makes judgment calls (what to remember, how to link, when to forget). No middleman, no extra inference cost. |
33 | 23 |
|
34 | 24 | | Pattern | LLM Role | Representative | |
35 | 25 | |---|---|---| |
36 | 26 | | **LLM-Embedded** | Executor inside the pipeline | Mem0, Letta | |
37 | 27 | | **MCP Server** | Tool provider via MCP protocol | claude-mem | |
38 | | -| **LLM-Supervised** | External supervisor of a standalone binary | Mnemon | |
| 28 | +| **LLM-Supervised** | External supervisor of a standalone binary | **Mnemon** | |
39 | 29 |
|
40 | 30 | <p align="center"> |
41 | 31 | <img src="docs/diagrams/llm-supervised-concept.jpg" width="720" alt="LLM-Supervised Architecture — three patterns compared, with detailed Mnemon implementation showing hooks, brain/organ split, and sub-agent delegation" /> |
42 | 32 | <br /> |
43 | 33 | <sub>The LLM-Supervised pattern: hooks drive the lifecycle, the host LLM makes judgment calls, the binary handles deterministic computation.</sub> |
44 | 34 | </p> |
45 | 35 |
|
| 36 | +Memory has a **compound interest effect** — the longer it accumulates, the greater its value. LLM engines iterate constantly, skill files cost nearly nothing to write, but memory is a private asset that grows with the user. It is the only component in the agent ecosystem worth deep investment. |
| 37 | + |
| 38 | +<p align="center"> |
| 39 | + <img src="docs/diagrams/10-knowledge-graph.jpg" width="720" alt="Knowledge Graph — 87 insights connected by temporal, entity, semantic, and causal edges" /> |
| 40 | + <br /> |
| 41 | + <sub>A real knowledge graph built by Mnemon — 87 insights, 2150 edges across four graph types.</sub> |
| 42 | +</p> |
| 43 | + |
46 | 44 | See [Design & Architecture](docs/DESIGN.md) for details. |
47 | 45 |
|
48 | 46 | ## Quick Start |
|
0 commit comments