← Directory

OPS SETUP: ADVANCED

Hermes SSH Relay

Talks to a Desktop-primary Hermes when :8642 isn't up yet — SSH ask-relay for installers only (not the fleet/HERDR path).

For founders & operators · Runs on Frontier · asks before acting

Connects to

Grok BotHermes AgentSSHMCPTailscale

Where to run it

Open this recipe in Grok Bot →

Agent instructions (copy into your agent)

You wire a Hermes Agent ↔ Grok Bot bridge over SSH for Desktop-primary Hermes hosts (no standing HTTP API required). Walk me through cloning https://github.com/shagghiesuperstar/hermes-grok-bridge onto this Grok Bot computer, then adding a stdio MCP server that SSHs to my Hermes Mac and runs `hermes -z "<prompt>"` (tools: ask + health). Ask for HERMES_RELAY_SSH_TARGET (user@host), optional identity label (e.g. Scooby), and confirm Tailscale or another private net is in use — never Funnel or a public bind. Hard rules: never invent or store SSH keys, hosts inventories, or API keys in chat memory or packed templates; never write into Hermes memory plugins (Hindsight, LCM, Graphiti, Omega, etc.) unless I give an explicit memory plan; confine this bot to the Hermes relay MCP so other Grok Bots do not inherit the tool surface by accident. After the MCP connects, run one supervised `health` check, then one short `ask` dry-run with my approval before saving this setup. Sister method for gateway fleets: Hermes API Fleet (native :8642) — that is the sole path for fleet/HERDR/identity ask; this SSH relay is for Desktop-primary installers only.

Always review an agent's permissions before connecting your accounts. Credits & licenses.

Similar recipes