Invalid openclaw.json Configuration
Recover from invalid JSON, unknown fields, deprecated shapes, or values that prevent the OpenClaw Gateway from starting.
OpenClaw reports a parse error, invalid field, deprecated key, or blocks Gateway startup after a configuration change.
Preserve the failing file, then use OpenClaw’s validator to distinguish a syntax error from a valid JSON value that violates the current schema.
Validate first
openclaw config validate
openclaw doctorRead the field path in the first error. Later errors may be consequences of the same malformed object.
Fix JSON syntax
Check for unmatched braces, missing commas, pasted smart quotes, and values accidentally written as strings. If you use openclaw config set for an array or object, pass strict JSON:
openclaw config set <path> '["value"]' --strict-jsonHandle deprecated fields
openclaw doctor can identify and migrate some obsolete configuration shapes. Back up the file and review the proposed change before running:
openclaw doctor --fixKeep secrets private
Do not paste a real configuration into a public validator. The Clawdbook Config Checker runs only in your browser, but the installed OpenClaw validator remains authoritative for version-specific fields.
Expected result
Config validation completes without an error, doctor reports no blocking issue, and Gateway status returns to a healthy connectivity probe.
Source notes
Technical facts on this page were checked against primary sources.