Memory Ferry
From its catalog listing
Migrates built-in Hermes MEMORY.md and USER.md records into a profile-local SQLite memory provider with an integrity-checked dry run, idempotent recovery, deterministic retrieval-parity evidence and migration-scoped rollback.
Good to know before installing
reads the active profile's memories/MEMORY.md and memories/USER.md; writes plaintext memories and full mode-0600 plan/export artifacts under $HERMES_HOME/plugin-data/memory-ferry (policy-blocked records remain in planning artifacts but are not imported or recalled); recalled snippets reach the user's configured model provider. No network calls, shell commands, credentials, telemetry or background process.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install memory-ferry - Said no? Turn it on later:
hermes plugins enable memory-ferry - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Memory & notes
- Maintained by
- gnanam1990 (Community)
- Needs
- No API keys declared
- Needs Hermes
- 0.23.1 or newer
- Version
- 0.1.0
- In the catalog
- 2026-11-12
Known issues (from its catalog listing)
- Only built-in MEMORY.md and USER.md are supported as migration sources; arbitrary external-provider export is unavailable through Hermes's public API.
- Retrieval parity is a bounded deterministic token-overlap measurement, not proof of semantic equivalence.
- The local approval receipt is digest-bound but not cryptographically signed, and the plugin has not received an independent production security audit.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in memory & notes
New Hermes Agent updates every day on X. Follow @HermesWatcher