OpenClaw Config Guard

Audit first. Repair only when the fix is proven. Protect startup over aesthetics.

Required Sources

Before making any judgment, open the official docs listed in references/official-sources.md. Treat them as the source of truth for schema, allowed values, and repair guidance. Do not rely on memory for config rules.

Workflow

1. 1. Resolve the active config path:

CODEBLOCK0

If that fails, fall back to ~/.openclaw/openclaw.json.

1. 2. Run a deterministic audit before touching the file:

CODEBLOCK1

This wraps:

• - INLINECODE1
• optional INLINECODE2

1. 3. Classify findings:

• - startup blockers: JSON5 parse failures, schema validation failures, unknown keys, wrong types, invalid enum values, missing required structure, or clearly conflicting settings that prevent startup.
• INLINECODE4: suspicious but non-blocking items such as duplicate plugin IDs, stale-but-working config, style cleanup, or non-critical hardening suggestions.

1. 4. Decide whether you may auto-fix:

• - Only auto-fix if the issue is a startup blocker.
• Only auto-fix if the docs or CLI output clearly show the correct repair.
• Prefer openclaw config set / openclaw config unset for exact path edits.
• Use manual JSON5 edits only when the CLI cannot express the required change and preserving comments or structure matters.
• Never run openclaw doctor --fix by default.
• Never restart OpenClaw by default.

1. 5. Backup before any write:

CODEBLOCK2

1. 6. Re-validate after any write:

CODEBLOCK3

If post-change validation fails, roll back immediately from the backup and say so in the report.

1. 7. Summarize what changed:

CODEBLOCK4

If you want a deterministic report frame, prepare a JSON manifest and run:

CODEBLOCK5

INLINECODE8 means the directory that contains this SKILL.md. Resolve relative paths against this skill directory instead of assuming any environment variable is set.

Decision Boundaries

• - Do not change non-blocking issues without user approval.
• Do not guess undocumented keys or values.
• Do not rewrite the whole config just to normalize formatting.
• Do not claim success without rerunning validation.
• Do not leave the user without a backup path, modified paths list, and post-change validation result.

Report Requirements

The final Markdown report must include:

• - official sources consulted
• active config path
• pre-change validation result
• startup blockers found
• automatic fixes applied
• issues intentionally not auto-fixed and why
• non-blocking recommendations for user decision
• modified config paths
• backup path
• post-change validation result
• whether manual restart is needed, and why

Resources

• - Official source list: references/official-sources.md
• Deterministic helper script: scripts/configguard.py