Hermes — Commander Multi-Agent Setup
Design and configure a multi-agent Hermes setup with a Commander agent that routes to specialist agents.
Current Focus
Drafting Commander AGENTS.md — the routing and orchestration layer for the multi-agent system. First specialist: #notes PKM agent.
Open Tasks
- Finalize Commander AGENTS.md (routing logic, shared context, handoff protocols)
- Design
#notesPKM specialist agent (context, skills, memory config) - Test Commander → PKM agent routing in a live session
- Define specialist agents needed beyond PKM (e.g. coding, research, brief generation)
Key Decisions / Insights
- Hermes natively supports AGENTS.md and MEMORY.md — no custom plugin needed
- MEMORY.md is agent-managed (2,200 char cap) — do not hand-edit
- Progressive subdirectory discovery means per-project AGENTS.md is powerful
- Commander pattern: one top-level AGENTS.md defines routing, each specialist has its own scoped config
- See hermes-agent-config for full config surface
Progress Log
2026-05-23
Verified that Hermes natively supports both AGENTS.md and MEMORY.md (via 175-source research task). Confirmed the four-file project context hierarchy and full configuration surface. Started drafting Commander AGENTS.md in the conversation. Session ended before specialist agents were designed — PKM agent (#notes) is the agreed first specialist to build.