auto-rollback_skill

Overview

This skill provides a backup and timed rollback safety net for changes to ~/.openclaw/openclaw.json on macOS using launchd. It creates a timestamped backup and schedules a rollback job before you edit the config, restoring the last-known-good file and restarting the Gateway if a restart fails. A BOOT.md hook can automatically cancel the pending rollback after a successful startup.

How this skill works

Before you modify openclaw.json you run the start command; the script copies the current config to a timestamped backup and writes a rollback-pending state. It schedules a launchd job that will run after 10 minutes to restore the backup and restart the Gateway if the system did not come back up. If the Gateway starts successfully, the bundled BOOT.md snippet cancels the pending rollback automatically; a manual cancel command is also available.

When to use it

• Before editing ~/.openclaw/openclaw.json
• When restarting the Gateway after config changes
• When remote access to the host is limited or risky
• When agents may modify configs without human oversight

Best practices

• Run skills/auto-rollback/auto-rollback.sh start --reason "brief description" before any config edits
• Append the provided BOOT.md snippet into your workspace BOOT.md to enable auto-cancel on successful startups
• Use the status command to verify rollback-pending state before editing
• Keep an AGENTS.md or SOP requiring agents to call start prior to changes
• Check rollback logs at ~/.openclaw/logs/rollback.log after any automatic recovery

Example use cases

• Apply a JSON change pushed by an agent on a remote host without remote shell access
• Test a new Gateway configuration and automatically revert if the service fails to restart
• Provide a safety net during scripted deployment or CI-driven config updates
• Ensure unattended agents can attempt safe updates with an automatic recovery plan