Hermes
Planner, editor, research coordinator, and final synthesis layer.
Hermes Under Omnigent
How Hermes appears in Omnigent's harness model and how to orchestrate it alongside Claude Code and Codex.
documented orchestration pattern inferred
Hermes is documented as a supported Omnigent harness. The README lists omnigent hermes, and the harness docs list both hermes and hermes-native. Sources: Omnigent README, harnesses.
What Omnigent adds around Hermes
Running Hermes under Omnigent should put Hermes inside the same common session model as other harnesses: web/mobile/desktop surfaces, shared sessions, policy checks, sandbox configuration, REST-accessible resources, and collaboration flows. This is inferred from the general harness documentation; there is no separate Hermes-specific deep-dive page in the public docs reviewed. Sources: coding agents, policy overview, OS sandbox config.
Practical orchestration pattern
Claude Code / Codex
Implementation or review sub-agents under a Polly-like workflow.
Omnigent
Common session, permissions, policy enforcement, sandboxing, and collaboration surface.
This pattern is not an official recipe; it is the natural result of Hermes being a supported harness and Polly demonstrating cross-agent coding orchestration. Sources: README built-in agents, MCP & tools.
Caution
Hermes-specific caveats beyond the harness names were under-documented in the public material reviewed. Treat exact CLI behavior as something to verify in a test Omnigent installation before making it part of production runbooks.