Onboarding Troubleshooting¶
Recommended triage order¶
When onboarding fails, start in this order:
loopforge config validateloopforge doctor<workspace>/.loopforge/onboard-report.md
Use this page when loopforge onboard or loopforge doctor reports warnings/errors.
1) Config invalid¶
Symptoms:
config invalid: ~/.loopforge/config.tomlconfig.parseis an error inloopforge doctor
What to do:
- Run
loopforge config validate - Fix TOML syntax or provider/router names
- Re-run
loopforge doctor
2) Provider unreachable¶
Symptoms:
ollama.httpwarning/error- onboarding fails with timeout / connection refused / HTTP request errors
What to do:
If you are not using Ollama, verify your configured provider base URL and credentials.
3) Model unavailable¶
Symptoms:
- onboarding fails with “model not found”
- first task cannot start even though the provider is reachable
What to do:
Then either:
- pull a local chat model, or
- update
[providers.ollama].default_modelin~/.loopforge/config.toml
4) Browser prerequisites missing¶
Symptoms:
browser.chromiumwarning- browser use cases fail before they can open a page
What to do:
- install a Chromium-based browser, or
- set
LOOPFORGE_BROWSER_CHROME_PATH, or - point
LOOPFORGE_BROWSER_CDP_HTTPto a live Chromium DevTools endpoint
5) Starter says success but the expected file is missing¶
Symptoms:
onboard-report.mdshowsexpected_artifact_missing- built-in starters like
workspace-briefdo not create their target file
What to do:
- inspect the saved session id in
<workspace>/.loopforge/onboard-report.md - retry the same task with the recommended
loopforge agent run ... --session ...command - if the assistant only printed JSON-like tool text, upgrade to this fix and retry
6) What file should I inspect first?¶
Open the most recent workspace report:
<workspace>/.loopforge/onboard-report.md
It is the fastest summary of:
- what passed
- what failed
- recommended next command
- suggested starter tasks