Series

Running a Hermes Agent Factory

Four Hermes instances on one model, kept apart by their harnesses: why agents are more than scheduled prompts, how engineering, product, growth and a personal assistant stay in their lanes, steering work from shared rooms, one skill registry for every harness, and the assistant-only calendar and inbox work.

5 parts · first published

Running a Hermes Agent Factory
  1. 01

    Agents Aren't Cron Jobs With a Personality

    Cron decides when work starts. An agent decides what happens next. Why I run four Hermes instances, and why the harness around a model matters more than the schedule that wakes it.

    ·5 min read
  2. 02

    Four Hermes Instances, One Model

    Engineering, product, growth and a personal assistant run as four separate Hermes instances on the same model. Each has its own VM, profiles, skills and boards, and a narrow way to reach the others.

    ·5 min read
  3. 03

    Steering Hermes Agents From One Place

    One shared room, @mentions and the Hermes web and mobile apps let me redirect four agent instances mid-task. The Google Photos to NAS migration shows how that works in practice.

    ·6 min read
  4. 04

    One Skill Registry for Every Harness

    Claude Code, Codex, Hermes and Pi get their agents and skills from one registry. Upstream skill packs are pinned to exact commits and never patched; changes are forks with provenance.

    ·5 min read
  5. 05

    Assistant-Only Work: Calendar and Inbox on Potts

    Inbox triage, a morning digest and calendar management run only on my assistant instance. Nothing else needs those skills or that Google grant, so nothing else gets them.

    ·4 min read
—
0:000:00