About this site

Why it exists

The Hermes agent is extensible by design: a plugin can add tools, hooks, a slash command and skills, and the difference between a good one and a fragile one is mostly in the parts nobody documents. This site exists to document those parts — the retry rules, the fail-open paths, the setting that changes behaviour, the failure you will otherwise debug twice.

Hermes and its ecosystem are developed by Nous Research. We do not work on Hermes. We build extensions for it, in public, with the source available on GitHub.

How the wikis are written

Each wiki starts from a code-level analysis of the plugin’s repository — its modules, entry points and data flow — and is then edited for the web: install steps, a reference for every command and setting, the design invariants, and a troubleshooting section drawn from the failure paths in the code.

Version numbers on these pages match the released plugin, not the repository’s main branch. When a plugin changes in a way a reader would notice, the wiki changes in the same release.

Standards we hold

• Every plugin runs its tests on Linux, macOS and Windows in CI.
• No telemetry, and no third-party request unless a feature genuinely needs one.
• State lives in plain files under $HERMES_HOME.
• Credentials are read through the host’s own secret scope, never a file we parse.
• No plugin is listed here before it ships, and no roadmap is published as a promise.

Publisher

Plugins for Hermes is published by Printaga Publishing LLC, which also publishes software, books and reference material for AI tooling. Questions, bug reports and corrections are best raised on the plugin’s GitHub repository.