Hermes Fleet as Life OS — Specialized Agents Per Domain Rather Than One Generalist
Core Idea
A fleet of specialized Hermes agents — one per life domain — outperforms a single generalist Hermes over time. Each specialist accumulates domain-specific MEMORY.md context without contaminating the others. The fleet is coordinated by a Commander AGENTS.md that routes tasks to the right specialist.
Why This Matters
A single generalist Hermes agent accumulates context from all domains (work, personal, health, money, etc.) into one 2,200-character MEMORY.md. This cap fills up with a mix of unrelated facts. A specialist agent’s MEMORY.md stays focused — every character is relevant to its domain. Over weeks, the specialist becomes meaningfully smarter in its domain while the generalist plateaus.
Candidate Architecture
Option A — Separate Hermes instances per life area
- One process per domain, each with its own SOUL.md, AGENTS.md, MEMORY.md, and session DB
- Most isolation; highest memory quality per domain
- Tradeoff: more config to manage, no cross-domain synthesis
Option B — Hermes sub-agents under a single Commander
- Commander Hermes receives all tasks and routes to specialists via Claude Agent SDK
- Specialists are stateless tools called by the Commander
- Tradeoff: simpler orchestration; specialists don’t accumulate independent memory
Option C — Hybrid hierarchy
- Commander handles routing and cross-domain synthesis
- Specialists run as isolated instances with their own memory
- Most powerful long-term; most setup complexity
Proposed Life Domains
Work, Think (learning/ideas), Body, Family, Money — five domains from the PARA + ACE expansion designed in W20.
Key Implication
AGENTS.md is the right place for per-domain rules in a multi-Hermes fleet. MEMORY.md accumulates automatically per-instance if Hermes instances are isolated per life area. The Commander’s AGENTS.md defines routing logic and handoff protocols between specialists.
Status (as of 2026-05-22)
Architecture being explored; no final design chosen. Conversation ended at the clarifying-questions stage.
Next step: define the life domains concretely and decide what each specialist agent would do differently from a generalist.
Connections
- hermes-agent-configuration — AGENTS.md and MEMORY.md mechanics for the fleet design
- hermes-agent-orchestration — ongoing effort tracking fleet architecture decisions
- hermes-commander-setup — Commander AGENTS.md draft in progress
Source
Conversation: “Hermes fleet architecture brainstorm” — 2026-05-22