OpenClaw Configuration Guide

OpenClaw stores its main configuration in openclaw.json. Use the CLI for routine changes when possible: it validates values and reduces accidental syntax errors.

Inspect before editing

openclaw status --all
openclaw config validate

Keep a local backup before a larger manual edit. Do not paste API keys into screenshots, issue reports, or public validation services.

Prefer focused CLI changes

The configuration command accepts a path and a value. For structured JSON values, use strict JSON mode so a string is not mistaken for an array or object.

openclaw config set agents.defaults.modelPolicy.allow '["openai/*", "ollama/*"]' --strict-json

After changing a setting, validate it before restarting the Gateway.

Validate and diagnose

openclaw config validate
openclaw doctor
openclaw gateway status

Use openclaw doctor --fix only after reading the proposed repair. A fix command can migrate deprecated shapes, but it cannot decide whether a permission or provider choice matches your intent.

Expected result

Validation exits without a schema error, doctor reports no blocking issue, and the Gateway connectivity probe remains healthy.

Private browser-side preflight

The Clawdbook Config Checker performs a lightweight JSON and risk preflight entirely in your browser. It does not upload configuration and does not replace openclaw config validate, which remains the authoritative check for your installed version.