OpenClaw 2026.9.7: check the upgrade path before restarting

Before you start

• Check current account access, plan and task requirements.

Documented change

The release improves backup coverage and upgrade recovery. Pre-June installations must bridge through 2026.9.5; rollback is conditional, not a promise that any running database can be restored automatically.

Who should care

Persistent-memory, scheduled and messaging deployments have state beyond a package version. Keep installation paths, service identity, channel credentials and database locations in the upgrade inventory.

A newer release is a reason to inspect the change log, not evidence that an existing workflow became more reliable.

Before and after

1. Record the current version and follow the documented bridge path where applicable.
2. Create a complete backup with enough free disk space; rehearse restore on a separate target.
3. After restart, check one real message, one fresh-session memory lookup and the next scheduled run.

Evidence and limits

Official documentation checked

• Source-backed facts plus BotClaw editorial interpretation. No product account, inference or agent performance test was run.

Sources

• https://docs.openclaw.ai/releases/2026.9.7
• https://docs.openclaw.ai/cli/backup

Continue the decision

• How do I upgrade an agent without losing working state?
• Verify a backup by restoring into a separate directory