Expand description
Messaging bridge framework — common types shared by all platform bridges.
Each bridge (Discord, Telegram, Slack, …) runs as a background tokio task. Inbound messages are injected into the reactive bus; outbound messages arrive via HTTP endpoint or MCP tool.
Modules§
- discord
- Discord messaging bridge — Gateway WebSocket + REST send.
- slack
- Slack messaging bridge — Socket Mode WebSocket receive + Web API send.
- telegram
- Telegram messaging bridge — long-polling
getUpdates+ REST send. - WhatsApp Cloud API messaging bridge — inbound webhook receiver + outbound
Graph API send. See
docs/specs/SPEC_MESSAGING_INTEGRATION_WHATSAPP_2026_07_07.md.
Structs§
- Bridge
Health - Embed
Field - Inbound
Msg - A message received from a messaging platform, normalized for reactive bus injection. Constructed in Phase 2 when per-message metadata is surfaced to the frontend.
- MsgEmbed
- Rich embed for platforms that support structured output (Discord, Slack).
- Outbound
Msg - A message to send to a messaging platform.
Enums§
Traits§
- Messaging
Bridge - Common interface implemented by every platform bridge (Discord, Telegram, …).