choose-hermes-agent-workflowlisted

# Choose Hermes Agent Workflow Classify the requested outcome before opening broad documentation or changing configuration. ## Route the Request | Requested outcome | Use | | --- | --- | | Install, update, configure, run, secure, troubleshoot, or use Hermes | `operate-hermes-agent` | | Create skills, plugins, providers, tools, hooks, desktop/dashboard extensions, or programmatic integrations | `build-hermes-agent-extensions` | | Run Hermes inside Zed, Xcode, or another ACP client | `operate-acp-agent-integration` plus the client-owning workflow | | Let Hermes discover, call, or be called by an independently operated peer agent | `operate-a2a-agent-integration` plus gateway operation for inbound service lifecycle | | Decide between ACP, MCP, TUI gateway, API, terminal, or native host integration | `choose-agent-integration-protocol` | | Run a messaging gateway, API server, webhook intake, messaging platform, or long-lived remote agent | `operate-hermes-agent-gateway` | | Use Nous Portal, Tool Gateway, Nous Chat, subscription proxy, or Hermes Cloud | `use-nous-research-services` | | Export Socket skills, translate Socket MCP, or classify Codex-to-Hermes portability | `hermes-agent-compatibility` | Use more than one workflow when the request genuinely crosses boundaries. Keep one workflow in charge of each write surface. ## Keep the Three Gateway Terms Separate - `Hermes messaging gateway`: the long-running Hermes process that connects messaging platforms, webhooks, and th