Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Memory Provider Plugins

Building a Memory Provider Plugin Memory provider plugins give Hermes Agent persistent, cross session knowledge beyond the built in MEMORY.md and USER.md. This

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/memory-provider-plugin

Building a Memory Provider Plugin Memory provider plugins give Hermes Agent persistent, cross session knowledge beyond the built in MEMORY.md and USER.md. This

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. Directory Structure
  2. The MemoryProvider ABC
  3. Required Methods
  4. Core Lifecycle
  5. Config
  6. Optional Hooks
  7. Config Schema
  8. Save Config
  9. Plugin Entry Point
  10. plugin.yaml
  11. Threading Contract
  12. Profile Isolation
  13. Testing
  14. Adding CLI Commands

Section map

Directory Structure

Maps directory structure to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

The MemoryProvider ABC

Maps the memoryprovider abc to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Required Methods

Maps required methods to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Core Lifecycle

Maps core lifecycle to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Config

Maps config to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Optional Hooks

Maps optional hooks to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Config Schema

Maps config schema to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Save Config

Maps save config to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide 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: Directory Structure, The MemoryProvider ABC, Required Methods, Core Lifecycle, Config. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: memory, provider, plugins, building, plugin. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

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

Verify firstDirectory Structure

Open the source anchor for Directory Structure 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for Directory Structure; 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 The MemoryProvider ABC 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

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