Hermes Agent doesn't just run in your terminal. It connects to 16 messaging platforms through a single gateway process, giving you AI assistance wherever you already communicate.
The Platform Landscape
| Platform | Region Focus | Key Feature |
|---|---|---|
| Telegram | Global | Most popular, voice notes, files |
| Discord | Global | Slash commands, threads, servers |
| Slack | Enterprise | Workflow triggers, channels |
| Global | 2B users, media, groups | |
| Signal | Privacy | E2E encryption, disappearing |
| Matrix | Federated | Self-hosted, open protocol |
| iMessage | Apple | Native iOS/Mac integration |
| China | 1.3B users, mini programs | |
| WeCom | China Enterprise | Corporate WeChat |
| DingTalk | China Enterprise | Alibaba's Slack |
| Feishu/Lark | China/Global | ByteDance collaboration |
| Mattermost | Enterprise | Self-hosted Slack alt |
| Universal | IMAP/SMTP everywhere | |
| SMS | Universal | Twilio, any phone |
| Home Assistant | IoT | Smart home voice bridge |
| Webhooks | Developers | Any custom integration |
Why Multi-Platform Matters
Meet users where they are. Your team uses Slack. Your family uses WhatsApp. Your Discord server has 10K members. One Hermes instance serves them all.
Cross-platform continuity. Start a conversation on Telegram, continue on Discord. Memory persists. Skills transfer. The agent knows who you are regardless of where you message from.
Resilience. If one platform has an outage, your agent is still reachable on others.
Architecture: One Gateway, Many Platforms
┌─────────────────────────────────────────┐
│ hermes gateway │
│ ┌─────────────────────────────────┐ │
│ │ Platform Adapters │ │
│ │ Telegram Discord WhatsApp │ │
│ │ Signal Matrix iMessage │ │
│ │ WeChat DingTalk Feishu │ │
│ │ Slack Email SMS ... │ │
│ └─────────────────────────────────┘ │
│ ↓ │
│ ┌─────────────────────────────────┐ │
│ │ Hermes Agent Core │ │
│ │ Memory · Skills · Tools │ │
│ └─────────────────────────────────┘ │
└─────────────────────────────────────────┘
The gateway translates platform-specific messages (Telegram photos, Discord slash commands, WhatsApp voice notes) into a unified format the agent understands.
Quick Setup Example: Telegram + Discord
# ~/.hermes/config.yaml
gateway:
platforms:
telegram:
enabled: true
# Token from @BotFather
discord:
enabled: true
# Token from Discord Developer Portal
hermes gateway start
Both platforms are now connected. Message on Telegram, the agent responds. Switch to Discord, same agent, same memory.
Platform-Specific Features
Telegram:
- Inline keyboards for tool approvals
- Voice message auto-transcription
- File upload with preview
- Webhook or polling mode
Discord:
- Slash commands (/ask, /task, /status)
- Thread support for long conversations
- Forum channel integration
- Role-based access control
iMessage (via BlueBubbles):
- Native Apple ecosystem feel
- Requires Mac running BlueBubbles server
- Full iMessage features: reactions, typing indicators
WeChat:
- Streaming responses with cursor
- Media uploads (images, voice, video)
- Markdown link handling
- Requires iLink Bot API
Security Considerations
Each platform has its own allowlist:
telegram:
allowedUserIds: [123456789]
discord:
allowedChannels: ["dev-chat", "ai-help"]
slack:
allowedUsers: ["U12345", "U67890"]
Unknown users receive a pairing code that you approve via CLI. No silent access.
Which Platforms Should You Enable?
Start with one platform you use daily — probably Telegram or Discord. Add more as needed:
- Personal use: Telegram + Signal
- Team/Work: Slack + Discord
- Enterprise China: WeChat + DingTalk + Feishu
- Privacy-focused: Signal + Matrix
- Universal fallback: Email + SMS