Channel Guides
Loong currently exposes 29 cataloged channel surfaces. Of those, 26 are already actionable public surfaces: 6 gateway-supervised service channels, 2 standalone native-serve surfaces, 15 config-backed outbound surfaces, and 3 external plugin-backed bridge surfaces. The remaining 3 surfaces stay catalog-only planned entries. Several gateway-supervised or standalone service lanes still reportimplementation_status=plugin_backed in inventory because the catalog preserves managed-bridge-capable setup contracts; this hub keeps that distinction visible instead of flattening it away.
Use Channels when you still need the conceptual model first. Use this hub when you already know the surface and want the exact config, command, and support boundary for that one channel. Keep Channel Recipes for representative rollout patterns rather than the full channel inventory.
Quick Picks
Use this short list when you want a practical starting point before scanning the full surface matrix below.| If you want… | Start here | Why |
|---|---|---|
| a primary team-chat runtime | Feishu/Lark | webhook and websocket paths are both documented on the most feature-rich managed-bridge-capable service channel |
| the lightest reply-loop bot | Telegram | it remains the smallest managed-bridge-capable service setup path |
| a Cloud API plus webhook runtime | send and serve are both shipped on the same managed-bridge-capable service surface | |
| the official enterprise AIBot lane | WeCom | the public docs keep the long-connection contract explicit while surfacing its managed-bridge-capable service model |
| a WeChat or personal WhatsApp bridge-first lane | Weixin, OneBot, or WhatsApp Personal | plugin-backed bridge surfaces stay visible and actionable instead of being flattened into placeholders |
| an official QQ runtime lane | QQ Bot | Loong now owns the native QQ gateway runtime directly |
| one operator-owned inbound webhook edge or one-way governed delivery | Webhook or Email | Webhook now covers the standalone native-serve lane, while Email remains a clean outbound-only example |
Gateway-Supervised Service Surfaces
These are the shipped send plus serve lanes that can currently join the daemon-owned gateway owner contract. Some still keepimplementation_status=plugin_backed in the catalog because their setup and transport metadata preserve managed-bridge-capable history.
| Surface | Transport | Send | Serve |
|---|---|---|---|
| Feishu/Lark | feishu_openapi_webhook_or_websocket | channels send feishu | channels serve feishu |
| Telegram | telegram_bot_api_polling | channels send telegram | channels serve telegram |
| Matrix | matrix_client_server_sync | channels send matrix | channels serve matrix |
| QQ Bot | qq_official_bot_gateway_or_plugin_bridge | channels send qqbot | channels serve qqbot |
| whatsapp_cloud_api | channels send whatsapp | channels serve whatsapp | |
| WeCom | wecom_aibot_long_connection | channels send wecom | channels serve wecom |
Standalone Native-Serve Surfaces
These surfaces ship send plus serve today, but their built-in runtime still stays on the directchannels serve <surface> command instead of gateway supervision.
External Plugin-Backed Bridge Surfaces
These surfaces are already real Loong channel contracts, but the active runtime is owned by an external bridge or managed plugin rather than a built-inchannels serve <surface> loop.
| Surface | Transport | Current operator path | Runtime owner |
|---|---|---|---|
| Weixin | wechat_clawbot_ilink_bridge | run loong weixin onboard, then verify with loong doctor / loong channels | external plugin |
| OneBot | onebot_v11_bridge | configure bridge contract + run loong doctor / loong channels | external plugin |
| WhatsApp Personal | whatsapp_web_baileys_bridge | run the bundled QR bridge, then use loong doctor / loong channels / grouped send/serve | external plugin |
Config-Backed Outbound Surfaces
These surfaces ship direct sends today and keep serve in the catalog without overclaiming a reply-loop runtime.| Surface | Transport | Send | Serve status |
|---|---|---|---|
| Discord | discord_http_api | channels send discord | outbound-only |
| Slack | slack_web_api | channels send slack | outbound-only |
| DingTalk | dingtalk_custom_robot_webhook | channels send dingtalk | outbound-only |
| smtp_imap | channels send email | outbound-only | |
| Google Chat | google_chat_incoming_webhook | channels send google-chat | outbound-only |
| Signal | signal_cli_rest_api | channels send signal | outbound-only |
| Twitch | twitch_chat_api | channels send twitch | outbound-only |
| Microsoft Teams | microsoft_teams_incoming_webhook | channels send teams | outbound-only |
| Mattermost | mattermost_rest_api | channels send mattermost | outbound-only |
| Nextcloud Talk | nextcloud_talk_bot_api | channels send nextcloud-talk | outbound-only |
| Synology Chat | synology_chat_outgoing_incoming_webhooks | channels send synology-chat | outbound-only |
| IRC | irc_socket | channels send irc | outbound-only |
| iMessage | imessage_bridge_api | channels send imessage | outbound-only |
| Nostr | nostr_relays | channels send nostr | outbound-only |
| Tlon | tlon_urbit_ship_api | channels send tlon | outbound-only |
Catalog-Only Planned Surfaces
These surfaces stay visible in the internal registry, but they are not yet public setup lanes and should not be marketed as shipped runtimes.| Surface | Registry role |
|---|---|
| Zalo | planned official-account surface |
| Zalo Personal | planned personal bridge surface |
| WebChat | planned embedded web inbox surface |
Reading Rule
- Start with Channels when you still need to choose between gateway-supervised, standalone native-serve, plugin-backed, and outbound-only delivery.
- Use an individual guide page when the surface is already decided and you need the exact config and smoke-test path.
- Plugin-backed guides are the right next stop when the transport is real but Loong intentionally leaves upstream login and listener ownership to an external bridge.
- Keep Channel Recipes for representative rollout paths instead of the full surface inventory.
- Keep Gateway And Supervision open whenever the chosen surface is gateway-supervised and needs long-lived ownership.