Check an upgrade against a recorded baseline

Before you start

• A verified backup and permission to restart this instance
• A recorded harmless task baseline

Prepare a comparison

1. Record CLI version, running gateway identity, release channel and configuration paths. Do not include secrets in the shared record.
2. Review the release notes relevant to your enabled channels and tools. Create and verify a backup before the change.
3. Run five small baseline checks: text response, read-only file access, a fresh-session memory check, private test-channel reply and one harmless scheduled event.
4. Follow the update method for your installation. Inspect completion and the actual running gateway version, then repeat the same checks.

Acceptance

Compare outputs at each seam, not just the updater’s exit code. If a formerly passing task fails, keep the before/after versions, failure evidence and recovery files. Pause recurring tasks affected by the failure before they repeatedly act on incomplete output.

Recovery and cleanup

Use the current official recovery method for the recorded installation. Do not delete migration originals or backups until the baseline passes and intended data is present. Restoring code alone may not reverse a state migration.

Evidence and limits

Official documentation checked

• Original BotClaw acceptance procedure based on linked official documentation. Product commands were not executed; check your installed version.

Sources

• https://docs.openclaw.ai/install/updating
• https://docs.openclaw.ai/cli/backup