Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Gateway Internals

The messaging gateway is the long running process that connects Hermes to 20+ external messaging platforms through a unified architecture. Key Files File Purpos

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/gateway-internals

The messaging gateway is the long running process that connects Hermes to 20+ external messaging platforms through a unified architecture. Key Files File Purpos

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. Key Files
  2. Architecture Overview
  3. Message Flow
  4. Session Key Format
  5. Two-Level Message Guard
  6. Authorization
  7. DM Pairing Flow
  8. Slash Command Dispatch
  9. Running-Agent Guard
  10. Config Sources
  11. Platform Adapters
  12. Token Locks
  13. Delivery Path
  14. Hooks

Section map

Key Files

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

Architecture Overview

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

Message Flow

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

Session Key Format

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

Two-Level Message Guard

Maps two-level message guard to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Authorization

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

DM Pairing Flow

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

Slash Command Dispatch

Maps slash command dispatch 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: Key Files, Architecture Overview, Message Flow, Session Key Format, Two-Level Message Guard. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: gateway, internals, messaging, running, process. 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 gateway internals before applying exact upstream commands.

Verify firstKey Files

Open the source anchor for Key Files 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 Key Files; 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 Architecture Overview 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

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

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