dvcrn Config Guardian
Overview
For Agent use only. Safe config updates with automatic backup, validation, and rollback. Prevents the agent from updating non-existent keys or invalid values.
When to Use
Use this skill every time you need to update openclaw.json. Prevents:
- Updating non-existent config keys
- Using invalid values
- Breaking the gateway with bad config
Workflow: Atomic Apply (Default)
For all config changes - handles everything in one command:
./scripts/atomic_apply.sh <config_path> <new_value>
# Example: ./scripts/atomic_apply.sh "agents.defaults.model.primary" "minimax-portal/MiniMax-M2.5"
What it does:
- Creates timestamped backup automatically
- Applies change via
openclaw config set <path> <value> - Validates with
openclaw doctor --non-interactive - Auto-rollback if validation fails
- Trap ensures rollback even on crash
Backup location:
~/.openclaw/config-guardian-backups/
Guardrails
- Never restart or apply config without explicit user approval
- Always use
atomic_apply.sh - If validation fails -> config auto-rolled back, don't force it
Scripts
| Script | Purpose |
|---|---|
atomic_apply.sh |
Default - all-in-one safe apply |
validate_config.sh |
Validate via OpenClaw doctor |
restore_config.sh |
Manual restore from backup |