Agent memory // Maintained forks & adaptations

Maintained

Mnemosyne Hermes

A local-first memory and orchestration adaptation for persistent agent work.

TL;DR Mnemosyne Hermes is a local-first memory and orchestration adaptation for persistent agent work. It pairs per-turn memory retrieval and writing with scheduled maintenance, and is published as an adaptation of rand/mnemosyne.

Year started
2026
Role
Author of this adaptation; based on rand/mnemosyne and materially extended for Hermes and related agent workflows.
Evidence stage
4/9: Publicly released
Last reviewed
2026-09-30
Problem

Agent work can lose useful context between sessions, while accumulated notes become hard to retrieve and maintain.

Who felt it

My own ongoing work with local-first agent tools.

Intervention

A two-loop design: a per-turn path for retrieving and recording relevant memory, paired with scheduled maintenance for auditing and connecting stored knowledge.

Role

Author of this adaptation; based on rand/mnemosyne and materially extended for Hermes and related agent workflows.

Started

2026

Stack

Python, SQLite, Hermes.

Constraints

Agent runtimes and model capabilities vary. Memory quality depends on the available context and the maintenance process; personal notes are not a public benchmark dataset.

Outcome

The code and an explanation of the design are public. Recall quality, reliability gains, and adoption have not been measured or published.

Limitations

No quantified recall or reliability improvement and no public adoption metrics. Personal memory data is not included as benchmark evidence.

Next step

Publish reproducible retrieval benchmarks using non-sensitive test data.