By name: openclaw-help description: "Help, FAQ, and testing for OpenClaw. Use when: looking up an everyday question about models, auth, or basic usage, finding a FAQ entry, running test suites (testing-live), or asking "how do I…" in plain language. For deeper diagnostics use openclaw-troubleshooting instead. Triggers on: "help", "faq", "how do I", "how to", "common question", "everyday", "basic usage", "testing", "testing-live", "codex agentic parity"."
OpenClaw Help Reference
FAQ
| Topic | When to use |
|---|---|
| First-run FAQ | Install stuck, onboarding errors, auth failures, first-run issues |
| Models FAQ | Model selection, auth profiles, failover, provider switching |
| Testing | Writing and running tests for OpenClaw agents |
| Testing live | Testing in production/live environments |
Common first-run issues
openclaw doctor is your first stop for any issue:
openclaw doctor --non-interactive
openclaw status
openclaw logs --follow
Install stuck? → First-run FAQ
Model auth failing? → Models FAQ
Channel not connecting? → openclaw channels status + channel troubleshooting
Testing
| Type | Tool |
|---|---|
| Unit/integration tests | openclaw test — see Testing |
| Live environment testing | Testing live |
| Channel diagnostics | openclaw channels diagnose |
Debug checklist
openclaw doctor --non-interactive— catches 80% of common issuesopenclaw status— gateway + agent healthopenclaw logs --follow— real-time gateway logsopenclaw gateway status— is the gateway process running?openclaw config get— verify active config matches expectations
References
references/faq-first-run.md— first-run and install issuesreferences/faq-models.md— model selection, auth, failoverreferences/testing.md— writing testsreferences/testing-live.md— live environment testing