Hermes Agent Control Room

What Hermes Agent Control Room does

The Agent Control Room is a folder or repository that sits beside your agents as a control plane. The README calls it the system map, operating manual, registry, runbook library and recovery notebook for the agents you run. Its core idea is to set up the Control Room first on a VPS, register one Hermes agent, and add direct specialists such as hermes-seo, hermes-dev, hermes-cmo and hermes-ops as roles become clear.

The template defines architecture levels: one agent, direct specialists, an optional orchestrator acting as a front door, and an automated team. For orchestrated work it describes an Agent Task Bus, with inbox, working, outbox and archive folders under /srv/agent-bus, for handoffs between the orchestrator and specialists. The repo supplies the folder structure, templates for agent runbooks, Docker notes, secret maps and backups, and bundled setup and operations skills that an agent can use to build or manage the system.

Key features

• Control Room folder structure for registry, rules, ports, env maps, runbooks and backups
• Level-based path from one agent to specialists to an orchestrated team
• Task bus pattern for orchestrator-to-specialist delegation
• Templates for agent runbooks, Docker notes, secret maps and backups
• Bundled setup and operations skills

When to use it

• Documenting a single Hermes agent on a new VPS
• Adding specialist agents for SEO, dev, marketing or ops with clear roles
• Planning a Docker migration of existing agents
• Recovering a setup from runbooks and backups

Who it is for: Operators running one or more Hermes agents on a VPS who want a documented, governed setup.

How it fits with Hermes Agent

Built around Hermes Agent: every agent it registers is a Hermes agent, and the template governs them from a side control plane.

FAQ