IA / Automatisation
1 juin 2026
Une commande : openclaw onboard sur Windows (WSL2) en 10 minutes
VpsGona Équipe
1 juin 2026
~12 min
openclaw onboard sous WSL2 en ~10 min. Docs Windows. déploiement, Ollama, bootstrap, passerelle headless.
Divulgation : location Mac optionnelle.
Pourquoi onboard
openclaw onboard --install-daemon → service systemd. Config ~/.openclaw/.
WSL2 vs natif
| Path | Command | Service | Use |
|---|---|---|---|
| WSL2 (recommended) | openclaw onboard --install-daemon | systemd user service | Full wizard + Linux tools |
| Native Windows | openclaw onboard | Scheduled Task / Startup | Quick CLI test |
| Native skip-health | openclaw onboard --non-interactive --skip-health | openclaw gateway run | When health blocks first run |
Prérequis
- WSL2, Node 22+, clé API
8 étapes
wsl --install- Mise à jour Ubuntu
- Node 22+
- Script install
openclaw onboard --install-daemon- Assistant
- Dashboard
gateway status
Assistant
Fournisseur, passerelle, canaux optionnels, skills.
Dépannage
Dashboard inaccessible
portproxy PORT.
Échec santé
--skip-health.
Suite
FAQ
What does openclaw onboard do?
It runs an interactive wizard that writes config under ~/.openclaw/, starts the gateway, and prints a dashboard URL.
Should I use --install-daemon?
Yes inside WSL2 for a systemd background service. Native Windows uses Scheduled Task fallbacks per official docs.
How long does setup take?
About 10 minutes after WSL2 and Node are ready; first wsl --install needs a reboot.
Can I skip Telegram/Slack in the wizard?
Yes—skip channels and run openclaw configure later.
Dashboard URL fails in Windows browser?
Use netsh portproxy to forward the WSL port to Windows localhost.