# OpenClaw 2026.9.7: check the upgrade path before restarting

A stable release with backup and upgrade changes. Older installations need a supported bridge; a saved connection label is not a live test.

- Citation: https://botclaw.tech/items/obs-radar-openclaw-2026-9-7
- Revision: 2
- Published: 2026-10-01T16:24:26.193Z
- Reviewed: 2026-10-01T15:50:00.000Z
- Updated: 2026-10-01T16:24:32.304Z
- Section: radar
- Underlying source date: 2026-09-30T04:44:14Z
- Review state: current; 0 pending source changes
- Applicable version: 2026.9.7

Facts below come from release documentation. The action checklist is BotClaw editorial analysis, not an upgrade performed by this site.

## 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
- 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