Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Plugins

Hermes has a plugin system for adding custom tools, hooks, and integrations without modifying core code. If you want to create a custom tool for yourself, your

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

Hermes has a plugin system for adding custom tools, hooks, and integrations without modifying core code. If you want to create a custom tool for yourself, your

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 overview
  2. Minimal working example
  3. What plugins can do
  4. Plugin discovery
  5. Plugin sub-categories
  6. Plugins are opt-in (with a few exceptions)
  7. What the allow-list does NOT gate
  8. Migration for existing users
  9. Available hooks
  10. Plugin types
  11. Pluggable interfaces — where to go for each
  12. NixOS declarative plugins
  13. Managing plugins
  14. Interactive UI

Section map

Quick overview

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

Minimal working example

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

What plugins can do

Maps what plugins can do to the Core Features documentation path, with the source page reserved for exact commands and updates.

Plugin discovery

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

Plugin sub-categories

Maps plugin sub-categories to the Core Features documentation path, with the source page reserved for exact commands and updates.

Plugins are opt-in (with a few exceptions)

Maps plugins are opt-in (with a few exceptions) to the Core Features documentation path, with the source page reserved for exact commands and updates.

What the allow-list does NOT gate

Maps what the allow-list does not gate to the Core Features documentation path, with the source page reserved for exact commands and updates.

Migration for existing users

Maps migration for existing users 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 overview, Minimal working example, What plugins can do, Plugin discovery, Plugin sub-categories. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: plugins, plugin, system, adding, custom. 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 plugins before applying exact upstream commands.

Verify firstQuick overview

Open the source anchor for Quick overview 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 overview; 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 Minimal working example 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

Source authority

Use the upstream source page for exact current behavior before applying configuration changes.

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