mnemon-dev/mnemon/hermes

mnemon

Use mnemon when durable memory can materially improve continuity across Hermes sessions. Hooks may inject recalled context before an LLM call, but the agent decides what is worth storing.

Workflow

1. Recall when prior decisions, preferences, or facts may affect the current task:

mnemon recall "<query>" --limit 10

1. Remember only stable, reusable knowledge:

mnemon remember "<fact>" --cat <cat> --imp <1-5> --entities "e1,e2" --source agent

1. Link related memories after reviewing candidates from remember:

mnemon link <id> <candidate> --type <causal|semantic> --weight <0-1>

Recall Intent

Keep focused queries and memories in their original language. When the user's meaning is clear, choose --intent WHY (reasons), --intent WHEN (timing), --intent ENTITY (what/who), or --intent GENERAL (neutral retrieval). For example: mnemon recall "<query>" --intent WHY. The override works in any language; --verbose reports meta.intent and meta.intent_source (auto or override).

Automatic cues cover some forms in English, Mandarin Chinese (simplified and traditional), Hindi (Devanagari), Spanish, Modern Standard Arabic, French, Bengali (Bengali script), Portuguese, Indonesian (Latin script), Russian (Cyrillic), and German. Unrecognized forms use GENERAL; conflicting cues involving additional languages also use GENERAL. English/Chinese-only scoring is preserved. This is a lexical heuristic, not full language understanding. See the supported forms, script variants, and limits.

Commands

mnemon remember "<fact>" --cat <cat> --imp <1-5> --entities "e1,e2" --source agent
mnemon link <id1> <id2> --type <type> --weight <0-1> [--meta '<json>']
mnemon recall "<query>" --limit 10
mnemon search "<query>" --limit 10
mnemon import --dry-run <file>
mnemon import <file>
mnemon forget <id>
mnemon related <id> --edge causal
mnemon gc --threshold 0.4
mnemon gc --keep <id>
mnemon status
mnemon log
mnemon store list
mnemon store create <name>
mnemon store set <name>
mnemon store remove <name>

Guardrails

• Do not store secrets, passwords, tokens, private keys, or short-lived operational noise.
• Prefer concise insights over transcript dumps.
• Categories: preference · decision · insight · fact · context
• Edge types: temporal · semantic · causal · entity
• Max 8,000 chars per insight.