19 · Back up, update, and verify

Update during a maintenance window, with a recovery path. Check the installed version and update information first:

openclaw --version
openclaw update status

1. Make a verified private backup

openclaw backup create --verify

Note the returned archive path. Archives can contain credentials, sessions, and workspaces: keep them private and outside a web root or public repository. Review what the backup covers; external services, separately stored files, and installed dependency trees may need their own backup/reinstallation plan.

2. Review and update

openclaw update

Read the updater's result. Supported package and source installs differ from containers, which must be updated through their image workflow. An exit code alone is not proof a new release was installed: an unsupported installation may be skipped. Follow any reported next action instead of repeatedly rerunning it.

3. Verify the running system

openclaw --version
openclaw gateway status
openclaw doctor
openclaw channels status --probe
openclaw cron list

Open the dashboard and send a small test chat. Check one important workflow and confirm scheduled jobs remain present. A restart is needed only where the update or configuration path calls for one.

If it fails

Record the error and inspect update status before another attempt overwrites useful evidence. Do not delete state, force-reinstall, or reset onboarding as a reflex. Follow the documented repair or restore path for your version. Backup restore extracts into a separate location; activation is a distinct operator step, not an in-place magic undo.