Recovery loop
- 1
Resolve the active file
Profiles and environment overrides can change the path.
openclaw config file --json - 2
Back up the exact file
Copy it to a verified location before using a writer or repair command.
- 3
Get structured findings
Read path, expected shape, and provider/source compatibility.
openclaw config validate --json - 4
Preview a targeted edit
Use dry-run and keep comments in mind: OpenClaw writers serialize as standard JSON.
openclaw config set <path> <value> --dry-run --json - 5
Revalidate
Restart only if the successful writer says the changed field requires it.
openclaw config validate openclaw doctor --json
Unknown provider params need owner documentation
The active schema can validate the surrounding provider structure while leaving provider-specific parameter bags open. Passing config validation does not prove every provider parameter is supported. Conversely, bundled third-party validators must not delete new or plugin-owned fields they do not understand.
Primary sources
Verify against the owner.
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.