hermes-outbound

原文涵盖的主题

• Hermes Outbound
• Freshness check
• Native vs pattern
• The outbound sequence
• Critical rules
• Sources

Guarantee that what leaves reads as if the owner wrote it: no internal notes, no machine traces, no caution jargon, no work files; the owner's tone, address form and signature; an exact preview shown before the go; a final scan by the chief that sends any draft with a single trace back for correction. Enforcement of "no send without go" is not a Hermes setting - it is built with hermes-security's go gate (native config, exact preview, then the owner's existing send mechanism). 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. | Piece | Status in 0.23.0 | Where | |-------|------------------|-------| | Approval for outbound email/messages | Not native. Hermes approvals cover dangerous terminal commands, MCP calls, optional memory/skill writes - not "send this email" | hermes-security | | "No send without go" | Pattern: approvals.deny on send commands, no send credenti

这里只展示节选，请以完整原文和当前要求为准。