fix(cli): offer config repair after invalid startup (#110533)

* fix(cli): offer doctor recovery for invalid config

* fix(cli): preserve invalid config overrides

* fix(cli): keep invalid config recovery controlled
This commit is contained in:
Peter Steinberger
2026-07-18 09:30:27 +01:00
committed by GitHub
parent ccf55a43cd
commit 1710313596
12 changed files with 537 additions and 28 deletions
+1
View File
@@ -33,6 +33,7 @@ openclaw gateway run # equivalent, explicit form
<AccordionGroup>
<Accordion title="Startup behavior">
- Refuses to start unless `gateway.mode=local` is set in `~/.openclaw/openclaw.json`. Use `--allow-unconfigured` for ad-hoc/dev runs; it bypasses the guard without writing or repairing config.
- When startup finds a repairable invalid config, an interactive terminal offers to run `openclaw doctor --fix` and retries startup once after consent. Non-interactive runs never repair automatically; they print the command instead. If the repaired config is still invalid, startup remains stopped.
- `openclaw onboard --mode local` and `openclaw setup` write `gateway.mode=local`. If the config file exists but `gateway.mode` is missing, that is treated as damaged/clobbered config and the Gateway refuses to guess `local` for you — re-run onboarding, set the key manually, or pass `--allow-unconfigured`.
- Binding beyond loopback without auth is blocked.
- `--bind` values `lan`, `tailnet`, and `custom` resolve over IPv4-only paths today; IPv6-only bring-your-own-host setups need an IPv4 sidecar or proxy in front of the Gateway.