Hermes: a scheduled agentic briefing on Hy3-preview

The Stack

Tested Against

Prerequisites

• Hermes Agent installed
• A gateway (Telegram/Slack/Discord) + OpenRouter key to actually run it

Steps

1. 1

   Define the scheduled job and validate cron + model

   Pin the provider (prices vary by host) and pick the model + a cron schedule for the briefing. Hy3 is not on Hermes' tool-use auto-list, so set tool_use_enforcement if it narrates. CI installs croniter, confirms the cron expression is valid and computes its next fire time, and asserts the model slug. It validates the cron and job config, not Hermes' internal scheduler.

   python3 -m venv .venv
   .venv/bin/pip install -q croniter pyyaml
   cat > briefing.yaml <<'YAML'
   model:
     provider: openrouter
     model: tencent/hy3-preview
   agent:
     tool_use_enforcement: true
   schedule:
     cron: "0 7 * * *"
   YAML
   .venv/bin/python - <<'EOF'
   import yaml
   from datetime import datetime
   from croniter import croniter
   cfg = yaml.safe_load(open("briefing.yaml"))
   model = cfg["model"]["model"]
   cron = cfg["schedule"]["cron"]
   assert model == "tencent/hy3-preview", f"bad model {model}"
   assert croniter.is_valid(cron), f"invalid cron {cron}"
   nxt = croniter(cron, datetime(2026, 1, 1)).get_next(datetime)
   print(f"briefing config OK: cron '{cron}' valid (next fire {nxt.isoformat()}) + model {model}")
   EOF

2. 2

   Wire the gateway and let it run (the model step, not checked by CI)

   hermes gateway setup connects Telegram/Slack/Discord; with a key set, the scheduled job searches, summarizes, and delivers. That run is the model step and is fenced.