> ## 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.

# Get Started

> The shortest path from install to first useful answer.

# Get Started

Use this section when you want the shortest path from install to a first useful
answer.

## Start Here

| If you want to...                                    | Start here                                          | Then continue to...                                                                             |
| ---------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| get one working local result as fast as possible     | [Installation](/get-started/installation)           | [First Run](/get-started/first-run) and [Doctor And Health](/get-started/doctor-and-health)     |
| get first value, then choose a provider deliberately | [Installation](/get-started/installation)           | [First Run](/get-started/first-run) and [Provider Guides](/use-loong/provider-guides/index)     |
| repair a broken first run before going deeper        | [Doctor And Health](/get-started/doctor-and-health) | [First Run](/get-started/first-run) again                                                       |
| get the CLI path healthy before adding channels      | [First Run](/get-started/first-run)                 | [Channel Guides](/use-loong/channel-guides/index) and [Channel Setup](/use-loong/channel-setup) |

## First Successful Outcome

The shortest supported path is still:

1. Install Loong.
2. Run guided onboarding.
3. Ask for one useful result.
4. Use `doctor` if setup is unhealthy.

The public docs lead with the base CLI path first. Channel setup, gateway surfaces, and richer runtime behavior come after the local assistant path is healthy.

## Reading Rule

* Install first.
* Run guided onboarding before touching deeper config.
* Use `doctor` as the repair path when the base CLI path does not feel healthy.
* Add providers, channels, and richer runtime surfaces only after the local assistant path works.

## Suggested Reading Order

* [Installation](/get-started/installation)
* [First Run](/get-started/first-run)
* [Doctor And Health](/get-started/doctor-and-health)

## What Comes Next

* If you want to understand provider choice and model selection after first run, continue to [Providers And Models](/use-loong/providers-and-models).
* If you want the practical provider and channel setup walkthroughs right away, go to [Provider Guides](/use-loong/provider-guides/index) and [Channel Guides](/use-loong/channel-guides/index).
* Keep [Provider Recipes](/use-loong/provider-recipes) and [Channel Recipes](/use-loong/channel-recipes) for representative rollout patterns after the exact built-in surface is clear.
* If you already know the target stack and want one complete rollout path, go to [Common Setups](/use-loong/common-setups) and then the dedicated playbook that matches it.
* If the next blocker is skill install, browser automation setup, or private-host and domain policy, continue to [Skills](/use-loong/skills) and [Browser And Web Boundaries](/use-loong/browser-and-web-boundaries).
* If you want to understand the current public runtime surface, continue to [Use Loong](/use-loong/overview).
* If you need the detailed channel matrix instead of the first-run path, jump to [Channels](/use-loong/channels).