​

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 report implementation_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.

​

Gateway-Supervised Service Surfaces

These are the shipped send plus serve lanes that can currently join the daemon-owned gateway owner contract. Some still keep implementation_status=plugin_backed in the catalog because their setup and transport metadata preserve managed-bridge-capable history.

​

Standalone Native-Serve Surfaces

These surfaces ship send plus serve today, but their built-in runtime still stays on the direct channels 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-in channels serve <surface> loop.

​

Config-Backed Outbound Surfaces

These surfaces ship direct sends today and keep serve in the catalog without overclaiming a reply-loop runtime.

​

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.

​

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.