github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-03-30 02:20:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: clarify windows onboarding gateway health

Browse Source
This commit is contained in:
Peter Steinberger
2026-03-13 02:40:25 +00:00
parent 23c7fc745f
commit b858d6c3a9
5 changed files with 100 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/cli/onboard.md
View File

@@ -95,6 +95,13 @@ openclaw onboard --non-interactive \
--accept-risk
```
Non-interactive local gateway health:
- Unless you pass `--skip-health`, onboarding waits for a reachable local gateway before it exits successfully.
- `--install-daemon` starts the managed gateway install path first. Without it, you must already have a local gateway running, for example `openclaw gateway run`.
- If you only want config/workspace/bootstrap writes in automation, use `--skip-health`.
- On native Windows, `--install-daemon` currently uses Scheduled Tasks and may require running PowerShell as Administrator.
Interactive onboarding behavior with reference mode:
- Choose **Use secret reference** when prompted.

27
docs/platforms/windows.md
View File

@@ -22,6 +22,33 @@ Native Windows companion apps are planned.
- [Install & updates](/install/updating)
- Official WSL2 guide (Microsoft): [https://learn.microsoft.com/windows/wsl/install](https://learn.microsoft.com/windows/wsl/install)
## Native Windows status
Native Windows CLI flows are improving, but WSL2 is still the recommended path.
What works well on native Windows today:
- website installer via `install.ps1`
- local CLI use such as `openclaw --version`, `openclaw doctor`, and `openclaw plugins list --json`
- embedded local-agent/provider smoke such as:
```powershell
openclaw agent --local --agent main --thinking low -m "Reply with exactly WINDOWS-HATCH-OK."
```
Current caveats:
- `openclaw onboard --non-interactive` still expects a reachable local gateway unless you pass `--skip-health`
- `openclaw onboard --non-interactive --install-daemon` and `openclaw gateway install` currently use Windows Scheduled Tasks
- on some native Windows setups, Scheduled Task install may require running PowerShell as Administrator
If you want the native CLI only, without gateway service install, use one of these:
```powershell
openclaw onboard --non-interactive --skip-health
openclaw gateway run
```
## Gateway
- [Gateway runbook](/gateway)