Skip to main content

​
Use Loong

Use this section when you already know Loong is relevant and need the public runtime model before diving into configuration details. The highlighted playbooks are representative rollout paths. The provider and channel pages keep the broader supported surface visible. This section is organized in two layers on purpose:
  • chooser pages explain which route fits
  • recipe and playbook pages show concrete config and command paths

​
Most Common Reading Paths

​
Page Types

  • Use chooser pages when you are still deciding which route fits.
  • Use guide pages when one provider or channel is already decided and you need the exact built-in contract.
  • Use recipe pages when you want representative rollout patterns, smoke tests, or sequencing.
  • Use playbooks when provider, channel, and ownership need to be treated as one rollout.
  • Use reference pages after the operator path is already clear.

​
Common Rollout Paths

If the stack is already clear, skip the generic recipe pass and start with one complete rollout path.

​
How To Read This Section

  1. Start with the base CLI path and make sure ask or chat works locally.
  2. Use Common Setups when the rollout shape is already clear and you want one proven route.
  3. Use Providers And Models or Channels when you still need to choose the right lane first.
  4. Drop into recipe pages when the chooser pages stop being concrete enough.
  5. Add channel or gateway surfaces only after the local assistant path is healthy.
  6. Turn on memory or skills flows when you need continuity or reuse rather than on day zero.

​
Current Public Runtime Shape

  • Assistant entrypoints: onboard, ask, chat, and doctor are the shortest public operator path.
  • Provider and model selection: onboard and runtime models list keep provider choice and model discovery visible instead of burying them behind one hardcoded provider story.
  • Operator runtime commands: audit, tasks, skills, plugins, channels, and runtime are part of the public surface.
  • Gateway ownership: gateway run, gateway status, and gateway stop cover the current owner flow for longer-lived delivery.
  • Delivery surfaces: Loong distinguishes runtime-backed reply-loop surfaces, plugin-backed bridge surfaces (including QR-linked personal-account bridges such as WhatsApp Personal), and a wider config-backed outbound inventory instead of flattening them into one story.
  • Governed runtime capabilities: tools, memory behavior, prompt defaults, policy, approval, and audit stay inside the same runtime model.

​
Page Guide