What problem does it solve? Connecting two Hermes agent gateways across servers fails in confusing ways: peer dm returns 404 when pointed at the wrong port, api_server silently binds to 127.0.0.1, cloud firewalls block new ports, and gateway restarts get intercepted by self-protection. This Skill provides the exact configuration steps, port layout, and troubleshooting playbook for linking Hermes gateways over the standard api_server + peer protocol. ## Core Features & Use Cases - Dual-side peer setup: Configure api_server (host 0.0.0.0, custom port, API_SERVER_KEY) on the new node and register it from the host with hermes peer add, then verify with hermes peer dm. - Cloud firewall handling: Detect the cloud provider (GCP/AWS metadata endpoints), attempt self-service firewall rules via gcloud SDK and metadata tokens, and fall back to SSH reverse tunnels when permissions are insufficient. - Troubleshooting playbook: Distinguish peer dm timeouts from channel failures via /health checks, work around gateway restart self-protection with at-scheduled scripts, and fix streaming truncation and multi-node config drift. - Use Case: You bought a new VPS and want a second Hermes agent to talk to your main one. Follow the checklist to enable api_server on both sides, exchange peer registrations, and verify a bidirectional closed loop. ## Quick Start Set up peer networking between my main Hermes gateway and the new VPS so the two agents can exchange messages.