Summary

hermes webhook list can report:

Webhook platform is not enabled.

while the Hermes gateway is actually serving the webhook adapter successfully from env-based runtime config.

In my repro, the webhook server is live and /health returns:

{"status": "ok", "platform": "webhook"}

but hermes webhook list still says webhook is disabled unless platforms.webhook is also written into ~/.hermes/config.yaml.

Root Cause

There are currently two different config-loading paths:

• gateway/config.py:load_gateway_config()

  • merges config.yaml
  • applies WEBHOOK_ENABLED, WEBHOOK_PORT, WEBHOOK_SECRET env overrides
  • gateway runtime works correctly from env-based config

• hermes_cli/webhook.py:_get_webhook_config()

  • calls hermes_cli.config.load_config()
  • reads config.yaml only
  • does not apply WEBHOOK_* env overrides

So the runtime and the CLI disagree about whether webhook is enabled.

Relevant Code

hermes_cli/webhook.py

def _get_webhook_config() -> dict:
    try:
        from hermes_cli.config import load_config
        cfg = load_config()
        return cfg.get("platforms", {}).get("webhook", {})
    except Exception:
        return {}

gateway/config.py

• load_gateway_config() explicitly documents env vars as highest priority
• _apply_env_overrides() sets Platform.WEBHOOK.enabled = True from WEBHOOK_ENABLED

Repro

1. Start Hermes gateway with env-based webhook config only, for example:
   • WEBHOOK_ENABLED=true
   • WEBHOOK_PORT=8644
   • WEBHOOK_SECRET=...
2. Do not write platforms.webhook into ~/.hermes/config.yaml.
3. Start the gateway.
4. Confirm the runtime is healthy:
   • curl http://127.0.0.1:8644/health
   • returns {"status": "ok", "platform": "webhook"}
5. Run:
   • hermes webhook list

Actual Result

hermes webhook list says webhook is not enabled.

Expected Result

hermes webhook list should use the same effective config source as the running gateway and recognize env-based webhook enablement.

Suggested Fix

One of these should happen upstream:

1. Make hermes_cli/webhook.py use gateway.config.load_gateway_config() for webhook state.
2. Or teach the webhook CLI path to apply WEBHOOK_* env overrides before checking platforms.webhook.

The key point is that the CLI and gateway should share one source of truth for effective webhook config.

Environment

• Hermes image: nousresearch/hermes-agent:v2026.4.8
• Reproduced in a containerized / managed deployment where the gateway runtime is configured via env vars and Kubernetes secrets.