Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Agent Loop Internals

The core orchestration engine is 's class — a large file that handles everything from prompt assembly to tool dispatch to provider failover. Core Responsibiliti

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

The core orchestration engine is 's class — a large file that handles everything from prompt assembly to tool dispatch to provider failover. Core Responsibiliti

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. Core Responsibilities
  2. Two Entry Points
  3. API Modes
  4. Turn Lifecycle
  5. Message Format
  6. Message Alternation Rules
  7. Interruptible API Calls
  8. Tool Execution
  9. Sequential vs Concurrent
  10. Execution Flow
  11. Agent-Level Tools
  12. Callback Surfaces
  13. Budget and Fallback Behavior
  14. Iteration Budget

Section map

Core Responsibilities

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

Two Entry Points

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

API Modes

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

Turn Lifecycle

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

Message Format

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

Message Alternation Rules

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

Interruptible API Calls

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

Tool Execution

Maps tool execution 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: Core Responsibilities, Two Entry Points, API Modes, Turn Lifecycle, Message Format. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: internals, orchestration, engine, class, large. 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 agent loop internals before applying exact upstream commands.

Verify firstCore Responsibilities

Open the source anchor for Core Responsibilities 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 Core Responsibilities; 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 Two Entry Points 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

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