hermes-gateways

Topics in the source

• Hermes Gateways
• Freshness check
• Native vs pattern
• Decision map
• Critical rules
• Workflow
• Sources

Connect one or more Hermes Agent profiles to messaging platforms through the single multiplexed gateway, route proactive output (briefs, alerts, decisions) to the right channel, and give the agent a voice that keeps working. Every key, flag and env var below was read in the official 0.23.0 docs or source; anything that is a design pattern rather than a Hermes feature is labelled Pattern. Before writing or changing any Hermes config, run hermes --version and hermes update --check, then read https://github.com/NousResearch/hermes-agent/releases/latest. If the installed or latest version is newer than 0.23.0, read every release note since 0.23.0 ("Upgrade notes" first) and adjust. Never apply guidance from this skill to a newer version without that check. | Need | Status in 0.23.0 | Where | |------|------------------|-------| | One gateway process serving every profile | Native, default (gateway.multiplexprofiles) | multiplex-gateway.md | | Slack / Telegram / Discord / Email adapters | Native, bundled platform plugins (auto-loaded) | messaging-adapters.md | | Several mailboxes for one owner | Pattern - one Email adapter = one mailbox per profile | messaging-adapters.md | | Proactive o

This is an excerpt. Refer to the complete source and its current requirements.