Hermes BibleUnofficial Docs
← All docs Docs / Reference

Toolsets Reference

Toolsets are named bundles of tools that control what the agent can do. They're the primary mechanism for configuring tool availability per platform, per sessio

Reference
Section
Reference
Source
hermesbible.com/docs/reference/toolsets-reference

Toolsets are named bundles of tools that control what the agent can do. They're the primary mechanism for configuring tool availability per platform, per sessio

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. How Toolsets Work
  2. Configuring Toolsets
  3. Per-session (CLI)
  4. Per-platform (config.yaml)
  5. Interactive management
  6. Core Toolsets
  7. Platform Toolsets
  8. Dynamic Toolsets
  9. MCP server toolsets
  10. Plugin toolsets
  11. Custom toolsets
  12. Wildcards
  13. Relationship to hermes tools

Section map

How Toolsets Work

Maps how toolsets work to the Reference documentation path, with the source page reserved for exact commands and updates.

Configuring Toolsets

Maps configuring toolsets to the Reference documentation path, with the source page reserved for exact commands and updates.

Per-session (CLI)

Maps per-session (cli) to the Reference documentation path, with the source page reserved for exact commands and updates.

Per-platform (config.yaml)

Maps per-platform (config.yaml) to the Reference documentation path, with the source page reserved for exact commands and updates.

Interactive management

Maps interactive management to the Reference documentation path, with the source page reserved for exact commands and updates.

Core Toolsets

Maps core toolsets to the Reference documentation path, with the source page reserved for exact commands and updates.

Platform Toolsets

Maps platform toolsets to the Reference documentation path, with the source page reserved for exact commands and updates.

Dynamic Toolsets

Maps dynamic toolsets to the Reference documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Reference 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: How Toolsets Work, Configuring Toolsets, Per-session (CLI), Per-platform (config.yaml), Interactive management. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: toolsets, reference, named, bundles, tools. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitReference documentation

Use when you need orientation for toolsets reference before applying exact upstream commands.

Verify firstHow Toolsets Work

Open the source anchor for How Toolsets Work 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 Reference, then open the linked source page for exact current syntax.
  2. Start with the source section for How Toolsets Work; 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 Configuring Toolsets 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