Skip to content
Mastery HQ Help

Hermes: the orchestrator

Hermes is Mastery HQ’s built-in orchestrator — the persona behind the Ninja pane. Where a normal agent writes code, Hermes manages: it interprets plain-language requests, drives the workspace (open, arrange, theme, status), dispatches tasks to your named agents, and reports outcomes back to you. Talk to it when you’d rather state intent (“get the tests fixed”) than direct each agent yourself.

Opening and talking to Hermes

Section titled “Opening and talking to Hermes”
  • Say/type open hermes (or Ctrl+Shift+H) — a violet Ninja window appears.
  • Address it from anywhere: hey hermes, minimize all agents and open the sprint board.
  • It runs the same command engine as the command bar, so anything you can command, Hermes can too — plus free-form requests that it reasons about with its configured brain.

The brain

Section titled “The brain”

Hermes thinks with a configurable backend (Settings → Hermes): the default is a relay to your own Hermes server, with Grok or other backends selectable when their keys are set. Connection status and tokens live in the same tab.

If your relay sits behind Cloudflare Access (for example, exposed at wss://hermes.yourdomain.com through a Cloudflare Tunnel and gated by a service token), fill in the connection’s Access Client ID and Access Client Secret in that same tab. Mastery HQ sends them as CF-Access-Client-Id / CF-Access-Client-Secret headers on the WebSocket handshake, so the edge lets the connection through; your device token still authenticates you to the relay underneath. Leave both blank for a plain Tailscale or ws:// relay.

What Hermes knows

Section titled “What Hermes knows”

Hermes can see the workspace state (who’s open, who’s running) and each agent’s persistent profile — the categories of work they’ve done, skills, and history. That’s the basis for routing: send the testing task to the agent who’s done the testing.

A taste

Section titled “A taste”

You: hey hermes, who’s working? Hermes: 2 working: Alex (fix login bug), Maya (write API docs). You: have Alex work on the signup card when he’s done. Hermes: Queued — assigning “signup flow” to Alex.

Hermes actions are confirmed in-app when they’re consequential, and everything lands in the Audit Log.