HERMES AGENT NOW PUSHES EVENTS TO ANY HTTP ENDPOINT YOU REGISTER. SIGNED WEBHOOKS. HMAC VERIFIED. YOUR CI, DASHBOARDS, AND AUTOMATIONS GET NOTIFIED WITHOUT POLLING. before webhooks: your dashboard polls Hermes every 30 seconds. "did anything happen? no. did anything happen? no." 288 empty checks per day. wasteful. after webhooks: Hermes pushes to your endpoint the moment something happens. zero polling. instant delivery. HMAC signed so your receiver verifies the event came from your agent, not a spoof. WHAT HERMES PUSHES: session started / ended turn completed (agent finished responding) tool call executed (which tool, what result) cron job fired task delegated to sub-agent approval requested / granted / denied each event = signed JSON payload delivered to your URL within seconds. HOW TO SET UP: tell your agent: "register a webhook endpoint at https: //myserver.com/hermes-events for tool_call and turn_completed events. sign with HMAC." or add to config.yaml: webhooks: - url: https:/ /myserver.com/hermes-events events: [tool_call, turn_completed, cron_fired] signing: hmac PRACTICAL USE CASES: DEPLOY PIPELINE: agent runs deploy skill → webhook fires to GitHub Actions → CI triggers build + test → result webhooks back to Hermes → agent confirms in Telegram: "deployed. tests pass." MONITORING DASHBOARD: every tool call → webhook → Grafana/Datadog. real-time visibility into what the agent does. token usage, tool frequency, error rates. no log parsing. structured events. HOME AUTOMATION: cron job completes morning research → webhook fires to Home Assistant → lights turn on. coffee machine starts. your morning brief arrives as the coffee brews. TEAM NOTIFICATIONS: agent finishes a long task → webhook to Slack channel → team sees "research complete, draft ready for review" without anyone checking Hermes. MULTI-AGENT COORDINATION: agent A completes research → webhook fires to agent B's endpoint → agent B starts writing based on the findings. event-driven pipelines between agents. WHY HMAC MATTERS: without signing: anyone who knows your endpoint URL can send fake events. your CI deploys on a spoof. with HMAC: every payload includes a signature computed from a shared secret. your receiver verifies the signature before processing. spoofed events get rejected.