Event Hooks
Hermes has three hook systems that run custom code at key lifecycle points: System Registered via Runs in Use case Gateway hooks + in Gateway only Logging, aler
- Section
- Core Features
- Source
- hermesbible.com/docs/user-guide/features/hooks
Hermes has three hook systems that run custom code at key lifecycle points: System Registered via Runs in Use case Gateway hooks + in Gateway only Logging, aler
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Gateway Event Hooks
- Creating a Hook
- HOOK.yaml
- handler.py
- Available Events
- Wildcard Matching
- Examples
- Telegram Alert on Long Tasks
- Command Usage Logger
- Session Start Webhook
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
Gateway Event Hooks
Maps gateway event hooks to the Core Features documentation path, with the source page reserved for exact commands and updates.
Creating a Hook
Maps creating a hook to the Core Features documentation path, with the source page reserved for exact commands and updates.
Available Events
Maps available events to the Core Features documentation path, with the source page reserved for exact commands and updates.
Examples
Maps examples to the Core Features documentation path, with the source page reserved for exact commands and updates.
Tutorial: BOOT.md — Run a Startup Checklist on Every Gateway Boot
Maps tutorial: boot.md — run a startup checklist on every gateway boot 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: Gateway Event Hooks, Creating a Hook, Available Events, Examples, Tutorial: BOOT.md — Run a Startup Checklist on Every Gateway Boot. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: event, hooks, three, systems, custom. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for event hooks before applying exact upstream commands.
Open the source anchor for Gateway Event Hooks and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
- Start with the source section for Gateway Event Hooks; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Creating a Hook if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
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