Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Architecture

This page is the top level map of Hermes Agent internals. Use it to orient yourself in the codebase, then dive into subsystem specific docs for implementation d

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

This page is the top level map of Hermes Agent internals. Use it to orient yourself in the codebase, then dive into subsystem specific docs for implementation d

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. System Overview
  2. Directory Structure
  3. Data Flow
  4. CLI Session
  5. Gateway Message
  6. Cron Job
  7. Recommended Reading Order
  8. Major Subsystems
  9. Agent Loop
  10. Prompt System
  11. Provider Resolution
  12. Tool System
  13. Session Persistence
  14. Messaging Gateway

Section map

System Overview

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

Directory Structure

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

Data Flow

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

CLI Session

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

Gateway Message

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

Cron Job

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

Recommended Reading Order

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

Major Subsystems

Maps major subsystems 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: System Overview, Directory Structure, Data Flow, CLI Session, Gateway Message. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: architecture, level, internals., orient, yourself. 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 architecture before applying exact upstream commands.

Verify firstSystem Overview

Open the source anchor for System 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for System 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 Directory Structure 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

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.

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