Safe update sequence
- 1
Inspect channel and availability
Record the current version and active stable/beta/dev selection.
openclaw update status --json - 2
Back up restorable state
Verify the archive before changing package or schema state.
openclaw backup create --verify - 3
Preview the plan
Confirm target, install method, plugin sync, and restart behavior.
openclaw update --dry-run --json - 4
Update and verify
Run interactively unless automation has an explicit policy.
openclaw update openclaw doctor --post-upgrade --json openclaw gateway status --require-rpc
When an update only partly completes
Use `openclaw update repair` when the core package changed but post-update plugin sync or repair did not converge. Do not repeatedly reinstall the package while the service, plugin metadata, or state migration is unresolved. Downgrades can be unsafe after schema or session-state migrations; restore only from evidence-backed backups and follow the release-specific guidance.
Primary sources
Verify against the owner.
Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.