Validate your config before starting: `openclaw config validate` (or `--json`). Catches invalid keys and gives actionable error paths.
Config validation before startup
Catch config errors before starting the gateway:
openclaw config validate
JSON output
For scripts or CI:
openclaw config validate --json
What it checks
- Valid JSON/JSONC structure
- Allowed keys and value types
- Plugin schema validation (AJV)
- Invalid-key paths with actionable hints
When it helps
- After editing config — Validate before restart
- CI/CD — Fail the pipeline if config is broken
- Troubleshooting — Get detailed error paths instead of generic startup failures
Startup errors now include detailed invalid-key paths so you know exactly what to fix.