MemoryRouter
Hermes Agent memory

Hermes memory: a provider swap, not a rebuild

Hermes treats memory as a provider: a component you select in configuration. That design makes the upgrade a config line instead of a migration project.

Hermes. Sources checked 2026-09-25.

How Hermes handles memory today

Hermes ships with a local memory provider, so recall depends on what is stored on the machine running the agent. Move the agent, rebuild the container, or clear state, and the memory goes with it.

The provider is configurable, and the published hermes-memoryrouter package registers MemoryRouter as a provider with the current Hermes release.

What Hermes Agent forgets

Local state is fast until it is gone.

The fix with MemoryRouter

Install the provider package, register it, and switch the active memory provider. Hermes keeps working the same way, with a durable store behind it.

  1. 1

    Install and register the provider

    Install and activate

    pip install hermes-memoryrouter
    hermes-memoryrouter install
    hermes config set memory.provider memoryrouter
  2. 2

    Provide the key

    Export MEMORYROUTER_API_KEY or place a memoryrouter.key file in your Hermes home with mode 0600. The package reads either.

  3. 3

    Verify recall

    Run a task that states a unique fact, then start a fresh session and ask for it. The provider answers from the vault rather than local state.

Install for Hermes

Package links, key handling, and verification on the Hermes page. 14-day free trial.

Related

Hermes Agent memory FAQ

Sources

Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.

Start free