Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Memory Providers

Hermes Agent ships with 8 external memory provider plugins that give the agent persistent, cross session knowledge beyond the built in MEMORY.md and USER.md. On

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/memory-providers

Hermes Agent ships with 8 external memory provider plugins that give the agent persistent, cross session knowledge beyond the built in MEMORY.md and USER.md. On

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Quick Start
  2. How It Works
  3. Available Providers
  4. Honcho
  5. New profile, fresh Honcho peer
  6. Existing profiles, backfill Honcho peers
  7. Per-profile observation
  8. Gateway identity mapping
  9. OpenViking
  10. Mem0
  11. Hindsight
  12. Holographic
  13. RetainDB
  14. ByteRover

Section map

Quick Start

Maps quick start to the Core Features documentation path, with the source page reserved for exact commands and updates.

How It Works

Maps how it works to the Core Features documentation path, with the source page reserved for exact commands and updates.

Available Providers

Maps available providers to the Core Features documentation path, with the source page reserved for exact commands and updates.

Honcho

Maps honcho to the Core Features documentation path, with the source page reserved for exact commands and updates.

New profile, fresh Honcho peer

Maps new profile, fresh honcho peer to the Core Features documentation path, with the source page reserved for exact commands and updates.

Existing profiles, backfill Honcho peers

Maps existing profiles, backfill honcho peers to the Core Features documentation path, with the source page reserved for exact commands and updates.

Per-profile observation

Maps per-profile observation to the Core Features documentation path, with the source page reserved for exact commands and updates.

Gateway identity mapping

Maps gateway identity mapping to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Quick Start, How It Works, Available Providers, Honcho, New profile, fresh Honcho peer. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: memory, providers, ships, external, provider. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for memory providers before applying exact upstream commands.

Verify firstQuick Start

Open the source anchor for Quick Start and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Quick Start; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for How It Works if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page