Mneme

A bright core inside a ring, joined by curved bundles of fine lines to five small rings around it, with dashed lines linking the small rings to each other.A bright core inside a ring, joined by curved bundles of fine lines to five small rings around it, with dashed lines linking the small rings to each other.

agent memory store with repeatable recall

Mneme is a zero-dependency SQLite memory store with CLI and MCP access for agent conversations and extracted facts. It stores session turns or imported source items, answers retrieval queries with deterministic BM25, vector, and recency ranking, and returns provenance, recall receipts, drift verdicts, replayable history views, and audited update or forgetting records.

Inspect sourceRun or verifyRead evidence
Status
active
Access
install
Release
v0.5.1 on GitHub and PyPI as flywheel-mneme
Checked
2026-09-26

Listed in the catalog under

Who it is for

Audiences

  • agent-system engineers
  • evaluation engineers

Deployment contexts

  • controlled agent workflows
  • review and CI lanes

Inputs and outputs

Inputs

  • an authorized session.json array of role/text turns
  • memory records and provenance
  • retrieval queries and filters
  • source snapshots
  • forgetting policy

Outputs

  • ranked memory recall
  • provenance and drift findings
  • temporal and user-scoped memory views
  • audited forgetting receipts

Run or evaluate

See it work, step by step An animated walkthrough with the real commands and output from the repository.

Entrypython -m pip install flywheel-mneme==0.5.1; mneme --help
Verificationmneme --state demo.db remember chat session.json --user alice; mneme --state demo.db recall "where does the user live" --user alice --json

Inspect the public source

Architecture and relationships

Related records

  • Relaycoding agent that acts within granted permissions
  • Forummulti-agent orchestration engine
  • Flywheelverified-inference platform and desktop client
Architecture, dependencies, and relationship notes

Dependencies

None declared in the public registry.

Relation-backed claims

  • Flywheel includes Mneme as a lane
    Flywheel 1.0.4 declares and launches Mneme as its memory MCP lane, pinned to flywheel-mneme 0.4.2. The pin trails the current 0.5.1 and is outside GHSA-j2pw-g7f4-9ppp, which names 0.5.0 only. Mneme remains an independently published package.

Current evidence

Mneme v0.5.1

Verified

How we know

The v0.5.1 GitHub release was published on 26 September 2026 (Pacific time) and attaches the wheel, the source archive and SHA256SUMS.txt. The wheel and source archive digests in SHA256SUMS.txt match the digests PyPI reports for flywheel-mneme 0.5.1. The release fixes the 0.5.0 forget command, which could keep erased text or erase another user's row while its receipt reported erased.

flywheel-mneme 0.5.1 on PyPI

Verified

How we know

PyPI serves flywheel-mneme 0.5.1. PyPI dates the upload 27 September 2026 in UTC, which is 26 September in Pacific time. A clean virtual environment installed it from PyPI on 26 September 2026, and pip reported the installed version as 0.5.1. This is distribution evidence; it does not establish that every feature works on every platform.

Mneme v0.3.0 downloads

Verified

How we know

Version 0.3.0 partitions source identity by user and session, supports named-user Gather imports, and checks source collisions before writing memory. Repeated imports preserve provenance. The released wheel and source archive were downloaded and checked against their hashes and accepted source. This is not provider-native session migration.

Download the v0.3.0 Python wheel

Verified

How we know

Wheel SHA-256 b709b685d667952b5461b93b435b180c2c1d19ca26c3dd0a9386ad9e847d72ea. A fresh installation completed isolated CLI ingest/recall/provenance and MCP remember/recall tasks. No real user database migration or adoption is established.

Mneme v0.3.0 source and examples

Verified

How we know

Tag v0.3.0 identifies commit dc0356abba92c27259b0d88587b66d82297b8da7. The README shows seeded remember/recall examples, source provenance, drift checks and MCP access. Recall requires imported source data; an empty store is not a completed memory task.

Limitations and authorization boundaries

  • Source recheck remains Mneme-owned rather than independently re-read by Crucible.
  • Replay rejects ambiguous SQLite sidecar or hardlink state.
  • Source partitioning does not implement provider-native continuation or automatically upgrade the separately pinned Flywheel memory lane.
  • Mneme publishes on PyPI as flywheel-mneme. The PyPI name mneme-memory belongs to another publisher.
  • flywheel-mneme 0.5.0 is affected by GHSA-j2pw-g7f4-9ppp; install 0.5.1 or later before erasing data.

Authorization boundary. Store and recall only information you are authorized to retain and process.