Selecting an External Memory Provider

Hermes built-in MEMORY.md and USER.md remain active when an external memory provider is enabled. The external provider is additive and can contribute semantic recall, automatic extraction, structured knowledge, or user modeling. Only one external provider is active at a time.

Official documentation: https://hermes-agent.nousresearch.com/docs/user-guide/features/memory-providers

Choose by operating requirement

Start with data location and control: local, self-hosted, or cloud. Then compare capture behavior, explicit write and delete tools, semantic search, user or peer identity, session strategy, dependencies, latency, and cost. A provider that automatically captures every turn has a different privacy and retention profile from one that stores only explicit facts.

Profile isolation must be verified rather than assumed. Provider configuration, local files, remote workspaces, peer identities, or container tags may all influence whether two Hermes profiles share or separate memory.

Selection checklist

  • Define which facts should outlive a session.
  • Decide whether data may leave the machine.
  • Compare automatic capture with explicit-write behavior.
  • Confirm search, update, delete, and export capabilities.
  • Define user, peer, workspace, and profile identities.
  • Set a context or recall budget.
  • Review provider pricing and dependency requirements.
  • Document an offboarding and deletion path.

Pitfalls

  • Enabling automatic capture before reviewing sensitive conversation scope.
  • Assuming built-in memory is replaced rather than retained.
  • Using one shared remote workspace when profiles require separation.
  • Measuring recall quality without measuring irrelevant context injection.
  • Choosing a cloud provider without testing deletion and export.

Verification steps

  1. Use hermes memory setup in a disposable profile.
  2. Confirm the selected provider with hermes memory status.
  3. Store one harmless, distinctive fact.
  4. Start a new session and test recall.
  5. Test search, update, and deletion when the provider supports them.
  6. Confirm another profile cannot see the fact unless sharing is intentional.
  7. Disable the external provider and verify built-in memory still works.
  8. Document data location, retention, and removal procedures before production use.