Channels
Use this page when the base CLI path already works and you need to choose the right delivery surface story before diving into commands or config fields. The base CLI path still comes first. A user should be able to succeed withask or chat before enabling service channels.
If you want the exact per-surface setup contract instead of the conceptual
surface map, go directly to
Channel Guides. Keep
Channel Recipes for representative rollout
paths, smoke tests, and multi-channel sequencing.
If you already know the provider and channel together, skip the narrower recipe
pass and go to Common Setups plus the dedicated
playbook that matches the rollout shape.
If you specifically need to choose between gateway run and
multi-channel-serve, continue to
Gateway And Supervision.
Already Know The Rollout Shape?
If the provider and channel are already obvious, skip this concept page and go straight to the matching playbook.| If you already know you want… | Go here |
|---|---|
| Volcengine plus Feishu or Lark | Volcengine Plus Feishu Or Lark |
| Volcengine plus WeCom | WeCom Rollout |
| BytePlus Coding plus Telegram | BytePlus Coding Plus Telegram |
| a local model plus outbound delivery | Local Model Plus Outbound Delivery |
| several runtime-backed channels on one host | Gateway Rollout |
Fast Path By Situation
| If you need… | Start with… | Why |
|---|---|---|
| Feishu or Lark should own a live team-chat runtime | Feishu/Lark | it is the shipped runtime family with webhook or websocket ownership |
| Telegram is enough for the live reply loop | Telegram | it is the smallest runtime-backed setup surface |
| Matrix should own a self-hosted or federated room runtime | Matrix | homeserver and room trust boundaries stay explicit |
| WhatsApp should own a Cloud API reply loop | direct sends and the webhook reply loop are both shipped | |
| WeCom should own the official enterprise AIBot lane | WeCom | it aligns with the shipped long-connection contract |
| outbound notifications without a reply loop | Channel Guides and Channel Setup | outbound-only surfaces stay visible without being overclaimed as runtimes |
| one host supervising several runtime-backed channels | Gateway And Supervision | owner commands, selectors, and rollout order live there |
Reading Rule
- Use this page to choose the delivery-surface lane.
- Use Channel Guides when one surface is already decided and you need the exact built-in contract.
- Use Channel Recipes when you need commands, smoke tests, or concrete config.
- Use Common Setups when provider and channel choice belong together.
- Use Gateway And Supervision when the real question is ownership, selectors, or long-lived supervision.
Choose The Right Surface Story
| Layer | What it means | Current examples |
|---|---|---|
| Base assistant loop | local operator-first path | onboard, ask, chat, doctor |
| Gateway owner contract | daemon-owned runtime control for longer-lived surfaces | gateway run, gateway status, gateway stop |
| Runtime-backed service channels | shipped reply-loop runtimes | Feishu / Lark, Telegram, Matrix, WhatsApp, WeCom |
| Config-backed outbound surfaces | shipped direct-send surfaces without a full reply-loop runtime | Discord, Slack, LINE, DingTalk, Webhook, Email, Teams, Google Chat, Signal, Twitch, and similar outbound integrations |
| Catalog or planned surfaces | inventory or future direction only | not presented as if a reply loop already ships |
Gateway And Runtime Ownership
gateway run,gateway status, andgateway stopare the current explicit owner contract for longer-lived delivery surfaces.multi-channel-serveis the compatibility wrapper that supervises the shipped runtime-backed service-channel subset.- Loong does not flatten gateway ownership, reply-loop runtimes, and outbound-only sends into one vague “channel support” story.
- Use Gateway And Supervision when you need the command-by-command ownership model, selector syntax, and rollout order in one place.
Runtime-Backed Service Channels
These are the shipped reply-loop runtimes today.| Surface | Transport shape | Primary commands |
|---|---|---|
| Feishu / Lark | webhook or websocket | loong feishu-send, loong feishu-serve |
| Telegram | Bot API polling | loong telegram-send, loong telegram-serve |
| Matrix | Client-Server sync loop | loong matrix-send, loong matrix-serve |
| Cloud API plus verified webhook service | loong whatsapp-send, loong whatsapp-serve | |
| WeCom | official AIBot long connection | loong wecom-send, loong wecom-serve |
Outbound Surface Families
These surfaces ship direct sends, config validation, and inventory metadata without claiming a full reply-loop runtime. This page keeps the concept layer short on purpose; the fuller field-level inventory remains in Channel Setup.| Surface family | Current examples | Typical command shape |
|---|---|---|
| workplace chat sinks | Slack, Discord, Microsoft Teams, Google Chat, Mattermost, Nextcloud Talk, Synology Chat | loong <surface>-send |
| messaging and bridge targets | LINE, DingTalk, Signal, IRC, iMessage / BlueBubbles, Nostr, Tlon | loong <surface>-send |
| direct delivery and alerting lanes | Webhook, Email, Twitch | loong <surface>-send |
Public Documentation Rule
Loong tries to keep the public channel story truthful:- the gateway contract is documented as the runtime owner contract
- shipped runtime-backed surfaces are documented as shipped
- outbound-only surfaces are documented as outbound-only
- catalog entries are not overclaimed as runtime support
Typical Progression
- Get the local assistant path healthy first.
- Add one shipped service channel if you need inbound or reply-loop automation.
- Use outbound-only surfaces when you need governed direct sends without pretending they are full runtime surfaces.
- Reach for
multi-channel-serveonly when you want multiple shipped service channels attached to the same CLI host.
Where To Go Next
- Continue to Channel Guides for the full shipped channel matrix.
- Continue to Channel Recipes for representative runtime-backed and outbound rollout examples.
- Continue to Channel Setup for the practical public setup guide.
- Continue to Gateway And Supervision for the longer-lived owner contract and channel-account selection rules.
- For the broader public runtime contract, continue to Use Loong.
- The full field-level source spec still lives in the repository’s public Channel Setup markdown.