Schema
The real path and real type matter
A config change should be schema-guided, not intuition-guided.
Change the smallest layer that solves the problem
Patch a narrow field or keyed entry instead of replacing the full parent object.
OpenClaw config
Safe config editing patterns for OpenClaw
Use this page when you need to make a config change without clobbering working settings, guessing structure, or widening a small edit into a larger outage.
Safe editing is a workflow
Inspect first, confirm the real path, patch narrowly, validate quickly, and verify runtime effect.
Start by naming the exact change
If the edit target is vague, the blast radius grows fast
Before touching config, decide exactly what field or behavior you are trying to change, which object owns it, and whether this is a narrow key update or a wider structural shift.
Inspect first, then edit
Look at the current shape before changing anything
The safest default habit is to inspect the current value and its surrounding object before editing. If the object is large, treat it as merge-sensitive until proven otherwise.
Core editing rules
Schema before guess, patch before replace
Patch
Validate
Do not queue up multiple changes and hope later
Validate right away so syntax mistakes, wrong paths, and wrong types do not spread.
Runtime
Structural success is not enough
A correct file edit still needs runtime verification because some settings hot-apply and others require restart.
If an edit goes wrong
Get smaller, not broader
Stop stacking more edits, isolate the smallest recent change, and restore the narrow broken layer first. Broad rewrites tend to compound damage instead of fixing it cleanly.