PROJECT Hermes plugin · open source · MIT
Discord Relay
One bot owns the conversation. A trusted bot can pass it one request.
Run several Hermes bots in one Discord server and a follow-up can turn into a chorus. A human mention chooses which bot handles a guild thread. A separate relay rule lets an explicitly trusted bot submit one request to an allowed existing thread.
Both capabilities are off by default. A send receipt does not mean the work is complete.
launch-check / thread 77
Launch plan review
Synthetic conversation
Maya human
@Builder check the launch plan.
- Conversation owner: Builder
Maya
And the rollback steps?
Builder handles this follow-up. Scout stays quiet.
BuilderBOT
I’ll include the rollback steps in the review.
- Later · one separate relay request
ScoutBOTID 2000
@Builder can you check the migration step too?
Maya asked Scout to pass this question here. One explicit relay request, shown without its envelope.
- Allowed route
- Scout → Builder
- Destination
- guild 4242 · thread 77
- Owner after relay
- Builder, unchanged
Native Hermes authorization must also allow Scout. No reverse route is granted. The sender's stop and the recipient's report are model instructions.
An independent Hermes plugin. Not affiliated with Discord.
01 · # conversation-rules
Keep follow-ups with one owner
Mention Builder in a guild thread. Builder handles unmentioned human follow-ups while other participating bots stay silent. Mention Scout to transfer the conversation to Scout. An authorized owner bot can also use a guarded handoff.
| Capability | What changes |
|---|---|
| Human mention or guarded owner handoff | Chooses the Hermes conversation owner. |
| Validated relay request | Admits one request into an exact allowed existing thread. Ownership stays unchanged. |
This ownership belongs to Hermes. Discord's own thread owner does not change. The plugin inherits the native Discord connection, tools, voice, media and slash commands. It makes no Discord API calls itself and does not synchronize servers or channels.
02 · # guarantees-and-limits
Know what is enforced
The receiver validates the exact sender, guild and thread, freshness and a bounded single-hop envelope. Durable receipts reject duplicate requests across restart. Unknown senders, unlisted destinations, self messages, webhooks, forwarded messages and nested relays are refused. An ordinary bot ping is not a relay request.
Bot provenance stays intact. Relay preserves native human authorization and approval requirements. Routes and payload text cannot grant human identity or consent. Authorize only the intended sender bot ID through the native policy. Its identity stays bot-authored; authorization does not turn it into a human.
The sender is instructed to send once, report the transport status and stop. The recipient is instructed to work in the destination thread and report directly to the human. These instructions do not restrict outbound tools or guarantee execution.
- Sent
- Discord stored the message. Recipient admission is unconfirmed.
- Admitted
- A durable receipt reserves local admission at most once. A crash after reservation can lose the task before dispatch.
- Completed
- The recipient reports the outcome to the human. A blocker means work remains. A send or admission receipt proves neither execution nor completion.
Ownership handoff defaults to bot_handoff: marker, which widens stock bot ingress for a guarded current-owner handoff. Set bot_handoff: off for ownership without that path. Relay is a separate opt-in and still needs its exact route and native authorization.
Source status and operational limits
Public source preview 1.1.0 at 2a751d0030fa006d868f896e57e1f8625854f4a1. No release tag or Hermes catalog listing is claimed. Live installation and guild acceptance must be verified separately.
Run one gateway writer per profile. Keep ownership JSON and SQLite relay receipts, including sidecars, during updates and rollback. Receipts are bounded to 4,096 records for 24 hours; storage failure or capacity denies new admission. Never reuse request IDs.
Compatibility and failure behavior · Bot ingress security note
03 · # setup
Run it yourself
Reuse an existing Hermes Discord bot. Read the native compatibility and security notes before enabling either capability. Choose the profile and exact sender/destination policy deliberately. Each profile keeps its own config, bot token, ownership cache and receipt database. Participating bots must trust the same humans to agree on ownership. Keep thread_require_mention: false for unmentioned follow-ups.
Ask your agent
Set up Discord Relay for my existing Hermes Discord bot. Source of truth: https://github.com/dmmeteo/hermes-discord-relay Read the README, compatibility, security note and migration guide first. Inspect the installed Hermes version and intended profile. Back up its configuration and preserve ownership and receipt stores. Follow the documented native install path. Ask me which bot should own the thread and which exact sender, guild and existing thread may relay. Keep native authorization and approval requirements. Never ask for tokens or secrets in chat. Use bot_handoff: off if I only want single-owner conversations. Align participating profiles on the humans they trust and keep thread_require_mention: false for follow-ups. Enable relay separately only for the exact route I approve. Keep DISCORD_ALLOW_BOTS=none. If native policy uses DISCORD_ALLOWED_USERS, ask before authorizing the exact sender bot ID there. Preserve its bot identity and every human approval boundary. Never enable open access or wildcard bot trust. Ask before restarting a gateway and wait for an idle boundary. Verify the installed adapter, then test with an authorized human in a dedicated thread. Distinguish transport, admission and completion. Report blockers honestly.
Install manually
hermes -p PROFILE plugins install dmmeteo/hermes-discord-relay --ref 2a751d0030fa006d868f896e57e1f8625854f4a1
hermes -p PROFILE plugins enable hermes-discord-relayReplace PROFILE with the intended profile name. For ownership alone, merge this into its existing Discord configuration:
discord:
thread_require_mention: false
thread_ownership_transfer:
enabled: true
bot_handoff: offRelay needs a separate opt-in, exact route and native sender authorization. Keep DISCORD_ALLOW_BOTS=none on both bots. Approve configuration changes and an idle-boundary gateway restart separately, then verify the installed adapter and test with an authorized human.
Already using the former install name? Follow the reversible identity migration. Keep the full Discord configuration and per-profile state. A new plugin label does not prove an already running adapter changed.