KI / Automatisierung
1. Juni 2026
Ein Befehl: openclaw onboard unter Windows WSL2 in 10 Minuten
VpsGona Team
1. Juni 2026
~12 Min.
openclaw onboard unter WSL2 in ~10 Min. Windows-Docs. Bereitstellung, Ollama, Bootstrap, Headless.
Hinweis: optionale Mac-Miete.
Warum onboard
openclaw onboard --install-daemon → systemd. ~/.openclaw/.
WSL2 vs nativ
| 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 |
Voraussetzungen
- WSL2, Node 22+, API-Schlüssel
8 Schritte
wsl --install- Ubuntu aktualisieren
- Node 22+
- Install-Skript
openclaw onboard --install-daemon- Assistent
- Dashboard
- Status prüfen
Assistent
Provider, Gateway, Kanäle optional, Skills.
Fehler
Dashboard timeout
portproxy.
Health-Fehler
--skip-health.
Weiter
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.