Onboard 跳过 API 凭据排障：补齐 provider 认证再进入渠道配置
用于“`openclaw onboard` 直接跳到 channel 配置，最终出现 No auth configured”场景。前置：全新安装或升级后首次向导。步骤：复现向导路径→检查配置中 provider/auth profile 是否缺失→补齐认证并重启→回归 QuickStart 向导。关键命令：`openclaw onboard`、`openclaw gateway status`。验证：向导会要求 provider/API key，完成后无缺失认证告警。风险：临时手工补丁可能在下次向导覆盖。
GITHUBDiscovered 2026-02-15Author nightclaw77
Prerequisites
- You can run onboarding wizard and inspect resulting gateway config safely.
- At least one valid model provider credential is available for testing.
Steps
- Run `openclaw onboard` in a clean environment and document whether provider-auth prompts appear.
- If prompts are skipped, inspect config for missing auth profile/default model bindings.
- Apply minimal auth fix, restart gateway, and rerun onboarding flow for validation.
- Add a post-onboard health check to fail fast when auth is absent.
Commands
openclaw onboardopenclaw gateway statusopenclaw gateway restartVerify
Fresh onboarding now asks for provider credentials and first reply succeeds without auth warnings.
Caveats
- Avoid storing plaintext keys in screenshots/logs while reproducing onboarding bugs.
- Behavior may differ between install methods (npm/curl/docker) and needs matrix verification（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗