hermes-channel-octo

What hermes-channel-octo does

The plugin talks to Octo over the WuKongIM binary WebSocket protocol, using ECDH key exchange and AES. It supports bot-to-user direct messages, group messaging, threads, @-mentions, and voice, video and file attachments. Hermes buffers text replies and sends one complete final message instead of streaming partial text.

One octo platform can hold several bot identities when OCTO_BOT_TOKEN contains a semicolon-separated list of tokens, one per Octo Space. Each token keeps its own WebSocket, heartbeat, event cursor and caches. The first message of a conversation binds it to the receiving identity by the bot's stable robot_id, so later replies, cards and media go back through the same bot, and rotating a token keeps existing chats. Only one token per Space can be used in a profile. A /octo_doctor command reports per-identity status, and the durable route registry holds up to 4096 target routes.

Key features

• Octo bot connection over the WuKongIM binary WebSocket protocol with ECDH and AES
• Direct messages, group messaging, threads and @-mentions
• Voice, video and file attachments
• Several bot identities through a semicolon-separated OCTO_BOT_TOKEN
• Durable per-conversation routing keyed by the bot's robot_id
• /octo_doctor command that reports per-identity status

When to use it

• Chat with a Hermes agent from a company Octo workspace
• Connect bots from several Octo Spaces to one Hermes profile
• Check which bot identities are connected with /octo_doctor

Who it is for: Teams that use Octo as their corporate messenger and want to reach a Hermes Agent gateway from it.

How it fits with Hermes Agent

Built for Hermes Agent as a channel plugin for the hermes-agent gateway.

Requirements: An Octo bot token, set as OCTO_BOT_TOKEN.

FAQ