Ultimate Hermes↔Grokbot Bridge

Use when wiring or operating any talk path between Grok Bot and Hermes in either direction (HTTP :8642, SSH relay, Hermes CLI, Tailscale webhook), or when choosing which path to use.

Use on the first conversation after importing the Ultimate Hermes↔Grokbot Bridge template — ask setup questions one at a time, then smoke both directions.

Use when talking to fleet Hermes, wiring hermes-* connectors, or anytime SSH relay tempts as a fallback — SOLE PATH is HTTP :8642.

Use when deciding between Hermes SSH Relay and Hermes API Fleet (:8642) for putting Hermes inside Grok Bot — fleet default is HTTP-only.

Use when an installer needs to enable Hermes :8642, verify health, or add a Tailscale-reachable hermes-<hostname> connector in Grok Bot.

Use when installing or wiring the Hermes SSH ask-relay MCP so a Grok Bot can talk to a Desktop-primary Hermes host over Tailscale.

Use this when setting up Tailscale (or any installed tool, daemon, or key) on the Grok Bot computer, when the computer may have been updated or reset, or when the bot can't reach tailnet hosts. It makes the setup survive a Computer Update and restore itself with no human step.

PUBLIC SANITIZED. Use for Public templates and Tailscale recovery with placeholders only — no live IPs, MagicDNS tails, machine names, secrets, or keys.

use this when documenting Hermes fleet Bitwarden secrets for messaging bots or any per-host credential — never share one TELEGRAM_BOT_TOKEN (or other per-host key) across hosts; store only FOO_<PROFILE> so Hermes auto-aliases per active profile