Membase vs MemoryRouter for Hermes: Does the Reply Get Saved?

John Rood··3 min read

You ask Hermes to name a maintenance job. It proposes paper-lantern-27, and you use the name in a planning call. The next morning you need it again, but it never appeared in anything you typed.

That's the question I'd settle before choosing an external memory provider: should it save the assistant's side of the conversation automatically?

Membase: Keep automatic capture on your side of the chat

The Membase listing in the Hermes Marketplace documents this behavior for Unibase's unibaseio-membase plugin. By default, automatic capture is off. The plugin can still recall before a turn, and you can ask Hermes to save a note with membase_save if the key has write access to a single Memory.

Turn on capture_turns and the plugin saves your words from a completed turn as a note. That automatic write leaves out the assistant's response. You can ask Hermes to save the name explicitly, but it won't get there just because Hermes proposed it.

That's a good fit when you want an external record of what you said, with an explicit decision about which of Hermes's suggestions to keep. Recall queries still go to Membase with capture off. The switch controls automatic writes, not whether the provider receives a query.

MemoryRouter: Keep the work that happened in the answer

I built MemoryRouter for the times when the useful part was worked out in the reply. In the Hermes provider's capture path, automatic capture saves your message and the final answer after the turn completes. It leaves out the raw tool results and internal reasoning. The saved text goes to the MemoryRouter vault behind your key; your model still runs through the inference provider configured in Hermes.

A recommendation in the vault isn't an approval. Before sending a draft or changing a runbook, check that you actually accepted the remembered suggestion.

Hermes activates one external provider at a time. You can leave its built-in memory in place. If the built-in files already hold everything you need next time, keep using them.

Try one detail that only Hermes supplied

Check versions first. The Membase 0.3.0 plugin manifest requires Hermes Agent 0.22.2 or newer. The published MemoryRouter setup and recall proof uses Hermes Agent 0.19.0 with hermes-memoryrouter 0.1.1 on Python 3.12. That's the verified end-to-end combination, not a claim about newer Hermes builds.

Use a test profile and synthetic data. Enable automatic capture for the provider you're testing. Give Hermes an invented job description and ask it to make up a distinctive label for the job. Don't repeat the label or ask Hermes to save a note.

Inspect the provider's stored note or exchange. First look for your job description to confirm a write happened. Then look for the label Hermes supplied. A search miss alone doesn't tell you what was stored.

Now start a new session and ask for the job's label without giving it away. Don't resume the old conversation or give Hermes access to the answer in its built-in files or session history. To try this with the MemoryRouter integration for Hermes, use the same key and core vault mode in both sessions.

Start with MemoryRouter and make that reply-only label your first recall test.