← Back to Setup and basicsOpenClaw config
Recovering from bad config without making it worse
Bad config recovery should be narrow, evidence-first, and calm. Panic edits usually create the second problem.
Recovery ruleConfirm what changed, isolate the break, back out only what is necessary, then verify the healthy baseline returned.
Recovery flow
The safe rollback path
- Identify the changed field. Do not recover blindly.
- Check the real symptom. Know whether the failure is parse, runtime, policy, or route behavior.
- Back out the narrow change. Restore the last known-good shape if needed.
- Verify the baseline. Check the exact route, behavior, or status that failed before.
Examples
Typical config recovery situations
Malformed JSONFix the syntax issue first before reasoning about higher-level behavior.
Wrong browser/network ruleRestore the narrower safe setting, then retry the exact blocked navigation.
Broken channel policyRestore the last known-good allowlist or mention setting, then test both paths.
Open deeper reference links for this page