Hermes Architecture Study Site

Read Hermes like a systems engineer, not like a tourist.

Hermes is not just an agent loop with a bag of tools. It is a layered runtime that separates execution, capabilities, state, memory, skills, delegation, and autonomy. This site turns the repository into a guided reading experience with chapters, checkpoints, and a side assistant for focused questions.

Architecture Lens

The four layers you should hold in your head before reading code

01

Entrypoints

CLI, TUI, Gateway, ACP adapter

02

Runtime

AIAgent loop, prompt assembly, context compression

03

Capabilities

tools, MCP, delegation, environments, file/web/browser

04

State

session DB, memory providers, skills, cron jobs

Reading Plan

Eight chapters, each built around one architectural judgment

How to Use It

Read one chapter at a time, then test your model of the system

Read the architecture claim

Each chapter starts with the one system decision that matters, not a dump of symbols.

Inspect the core file paths

Source references point you to the files that define the behavior, so you can verify every claim.

Answer a checkpoint

Every chapter ends with a choice question to force a mental model, not passive familiarity.

Use the side assistant only when stuck

The drawer carries chapter context so you can ask sharper questions without losing your reading flow.