First Run
Supported First-Run Loop
Continue The Session
When you need follow-up work:What Success Looks Like
loong onboardfinishes without leaving you in raw config editing as step zero.loong askproduces one useful answer.loong chatis available for follow-up work.loong doctoris there as the repair path if something still looks off.
If First Run Feels Incomplete
Go straight to Doctor And Health when:- credentials were not detected cleanly
- the provider path still feels ambiguous
askorchatdoes not behave like a healthy local assistant path
Approximate Config Shape
api_key = { env = "PROVIDER_API_KEY" }means “read the secret from that environment variable”.api_key = "PROVIDER_API_KEY"would instead be treated as the literal API key value itself.- The docs standardize on the
{ env = "..." }shape because it is explicit and matches the wider secret-reference model.
Why This Page Stays Short
- The first-run handoff should get you to one useful answer quickly.
- Provider matrices, channel matrices, and richer runtime policy details belong in deeper guides.
- The local CLI success path should come before gateway, channels, or broader product surfaces.
What Comes Next
- Continue to Providers And Models if you want the public provider and model-selection contract.
- Continue to Doctor And Health if the first run is incomplete or unstable.
- Continue to Use Loong once the base operator path is healthy.