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 | First Run and Doctor And Health |
| get first value, then choose a provider deliberately | Installation | First Run and Provider Guides |
| repair a broken first run before going deeper | Doctor And Health | First Run again |
| get the CLI path healthy before adding channels | First Run | Channel Guides and Channel Setup |
First Successful Outcome
The shortest supported path is still:- Install Loong.
- Run guided onboarding.
- Ask for one useful result.
- Use
doctorif setup is unhealthy.
Reading Rule
- Install first.
- Run guided onboarding before touching deeper config.
- Use
doctoras 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
What Comes Next
- If you want to understand provider choice and model selection after first run, continue to Providers And Models.
- If you want the practical provider and channel setup walkthroughs right away, go to Provider Guides and Channel Guides.
- Keep Provider Recipes and 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 and then the dedicated playbook that matches it.
- If the next blocker is managed skill install, browser preview, or private-host and domain policy, continue to Managed Skills and Browser And Web Boundaries.
- If you want to understand the current public runtime surface, continue to Use Loong.
- If you need the detailed channel matrix instead of the first-run path, jump to Channels.