openclaw - 💡(How to fix) Fix Windows post-onboarding provider switch path is not discoverable

Summary

On Windows, the post-onboarding provider switch path is not discoverable. openclaw onboard --auth-choice <provider> implies the key prompt will appear, but the user must choose "Review and update" first. That dependency is not signposted.

Environment

• OS: Windows 11 Version 25H2
• OpenClaw: 2026.5.27 (27ae826)
• Node: v24.16.0
• Install method: PowerShell install script / QuickStart
• Terminal: Windows PowerShell

Steps to reproduce

1. Complete onboarding with one provider.
2. Attempt to switch to another provider post-onboarding.
3. Run:

   openclaw onboard --auth-choice groq-api-key

4. Observe the wizard presents "Review and update" vs "Start fresh".
5. Select the wrong path or proceed without selecting "Review and update".

Expected result

The --auth-choice flag should route directly to the provider credential prompt, or the wizard should explicitly say:

To enter/update this provider key, choose "Review and update".

Actual result

No API key prompt appears unless the user knows to pick "Review and update". The correct path exists but is not discoverable from the flag name or wizard wording.

Impact

Low-to-medium onboarding friction. A beginner user will likely assume provider switching is unsupported or broken.

Suggested fix

• Route --auth-choice directly to the relevant provider credential step when safe.
• Rename/annotate "Review and update" to indicate it is the key-update path.
• Add a documented Windows provider-switch command to the onboarding completion output.

Source

HeraldLabs beta QA report from Miriam Peter, 2026-05-30.