> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loongclaw.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Setups

> End-to-end setup playbooks that combine providers, channels, and gateway ownership.

# Common Setups

Use this page when `onboard`, `ask`, or `chat` already makes sense and you want
one practical setup shape instead of reading provider, channel, and gateway
pages separately.

This page is now the setup hub, not another long cookbook. The detailed
operational steps live in dedicated playbooks.
If you want the shared public config shape before you pick a playbook, start
with [Configuration Patterns](/use-loong/configuration-patterns).

## Start With The Common Cases

These playbooks cover a few repeatable rollout shapes. They are representative
paths, not the full support matrix. Use
[Provider Guides](/use-loong/provider-guides/index) and
[Channel Guides](/use-loong/channel-guides/index) when you want the broader
family-by-family map instead of one end-to-end playbook. Keep
[Provider Recipes](/use-loong/provider-recipes) and
[Channel Recipes](/use-loong/channel-recipes) for representative patterns.

All routes here stay inside the current public contract:

* managed-bridge-capable service channels currently surface to operators as
  Feishu / Lark, Telegram, Matrix, WhatsApp, and WeCom
* outbound-only surfaces stay outbound-only
* `gateway run` remains the explicit owner contract for longer-lived service
  supervision
* grouped operator shells such as `runtime`, `channels`, and `gateway` are the
  canonical docs surface

## Choose A Playbook

| If you want...                                         | Start here                                                                    | Why                                                                                         |
| ------------------------------------------------------ | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| one hosted provider plus a Feishu or Lark team room    | [Volcengine Plus Feishu Or Lark](/use-loong/volcengine-feishu-lark-playbook)  | it keeps the primary hosted and team-chat path together                                     |
| WeCom as the long-lived enterprise lane                | [WeCom Rollout](/use-loong/wecom-rollout-playbook)                            | it matches the shipped AIBot long-connection contract                                       |
| a dedicated coding lane plus a lightweight bot surface | [BytePlus Coding Plus Telegram](/use-loong/byteplus-coding-telegram-playbook) | coding traffic and runtime delivery stay explicit                                           |
| a local model plus governed outbound delivery          | [Local Model Plus Outbound Delivery](/use-loong/local-outbound-playbook)      | local inference and outbound notifications stay separate from reply-loop runtimes           |
| several service channels on one host                   | [Gateway Rollout](/use-loong/gateway-rollout-playbook)                        | it moves from one healthy managed-bridge-capable service lane to explicit gateway ownership |

If you still just need one provider to work locally, go back to
[First Run](/get-started/first-run) and
[Provider Guides](/use-loong/provider-guides/index) instead of treating this
hub like a provider-only guide.

## Shared Validation Loop

Use the same short loop after each setup slice:

```bash theme={null}
loong doctor
loong runtime list models
loong channels
```

When gateway ownership is involved, add:

```bash theme={null}
loong gateway status --json
loong status --json
```

Use `gateway status --json` for the shortest ownership-specific view and `status --json` for the broader operator summary across gateway, ACP, and work-unit surfaces.

## Reading Rules

* Start with the base CLI path first. Do not treat a channel or gateway setup
  as step zero.
* Use [Configuration Patterns](/use-loong/configuration-patterns) when the
  rollout is clear but you still want the shared provider, account, and memory
  shape before a playbook.
* Use a dedicated playbook when the rollout shape is already clear.
* Use provider-only or channel-only recipe pages when the setup is still narrow.
* Move to gateway selectors only after named `accounts.<id>` entries exist.

## Continue Reading

| If you want to...                                       | Go here                                                                                                 |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| stay on the main hosted team-chat lane                  | [Volcengine Plus Feishu Or Lark](/use-loong/volcengine-feishu-lark-playbook)                            |
| follow the WeCom-specific enterprise path               | [WeCom Rollout](/use-loong/wecom-rollout-playbook)                                                      |
| follow the dedicated coding-plus-bot route              | [BytePlus Coding Plus Telegram](/use-loong/byteplus-coding-telegram-playbook)                           |
| use a local model without overclaiming delivery support | [Local Model Plus Outbound Delivery](/use-loong/local-outbound-playbook)                                |
| supervise several runtime-backed channels               | [Gateway Rollout](/use-loong/gateway-rollout-playbook)                                                  |
| inspect the shared public config shape first            | [Configuration Patterns](/use-loong/configuration-patterns)                                             |
| step back to provider-only setup                        | [Provider Guides](/use-loong/provider-guides/index) and [Provider Recipes](/use-loong/provider-recipes) |
| step back to channel-only setup                         | [Channel Guides](/use-loong/channel-guides/index) and [Channel Recipes](/use-loong/channel-recipes)     |
| inspect the owner contract directly                     | [Gateway And Supervision](/use-loong/gateway-and-supervision)                                           |
| return to the wider runtime map                         | [Use Loong](/use-loong/overview)                                                                        |