Mnemix
Mnemix is a local-first memory engine for AI agents and related tools. It gives an agent a durable store for decisions, facts, procedures, summaries, and preferences without requiring a hosted service or background daemon.
The project is built around three ideas:
- memory should be structured, not just a raw transcript dump
- recall should be layered so agents get the smallest useful context first
- history should remain inspectable so restore and recovery are safe
What Mnemix provides
- scoped memory for repositories, workspaces, or other contexts
- typed memory records for observations, decisions, preferences, facts, procedures, and summaries
- layered recall with pinned context, summaries, and archival expansion
- full-text search across stored memories
- optional vector-ready persisted embeddings for semantic and hybrid retrieval backends
- checkpoints and version history for recovery
- a terminal-first CLI with optional JSON output
- a thin Python client built on the CLI contract
- workflow-specific host adapters built on the Python client
How it works
An agent writes memories to a local store with remember. Later sessions use recall, search, pins, or show to pull back the right amount of context.
Retrieval model
Recall is designed to expose the most useful context first:
| Layer | Purpose |
|---|---|
pinned_context | Always-available, intentionally elevated context |
summaries | Compact, high-signal memories for normal recall |
archival | Broader historical matches for deeper inspection |
This progressive disclosure model helps keep context windows focused while preserving access to the full store.
Quick start
Install from PyPI:
pip install mnemixInitialize a store:
mnemix --store .mnemix initWrite a memory:
mnemix --store .mnemix remember \
--id memory:first-decision \
--scope repo:mnemix \
--kind decision \
--title "Adopt Mnemix for persistent agent memory" \
--summary "Use a local structured store instead of raw transcript recall." \
--detail "Mnemix keeps memories inspectable, searchable, and versioned." \
--importance 85Recall context for the next session:
mnemix --store .mnemix recall --scope repo:mnemixSearch for a specific topic:
mnemix --store .mnemix search --text "persistent agent memory" --scope repo:mnemixInterfaces
- The CLI is the primary user-facing interface.
- The Vector Retrieval page explains the optional vector layer, coverage reporting, and current CLI limits.
- The Python client wraps the CLI's
--jsoncontract. - The Host Adapters page shows how to shape recall and writeback for coding, chat, CI, and review workflows.
- The Policy Runner page shows how to combine guided memory usage with required workflow checkpoints.
- The Mnemix Workflow page explains the repo-native planning methodology and the companion
mxwCLI. - The storage foundation explains why Mnemix uses LanceDB and Lance underneath.
Ecosystem
Mnemix is also part of a broader toolchain. For config-driven, multi-platform generation of AI coding resources, see mnemix-context.
Next steps
- Read Memory Model for the shape of stored records.
- Read Vector Retrieval for store-level vector settings and semantic retrieval readiness.
- Read Versioning & Restore for recovery semantics.
- Read Checkpoint & Retention Policy for safety defaults.