Reinventing.AI

OpenClaw Trends

OpenClaw 2026.11.5 Rolls Back Failed Updates as Extended-Stable 2026.10.33 Ships

OpenClaw 2026.11.5 boots a new release once before trusting it and restores the previous version when Doctor or Gateway startup fails. A day later, the 2026.10.33 extended-stable release gave operators a slower update line.

AI Agent Insights Team6 min
OpenClaw Update Rollback and Extended-Stable Channel

The OpenClaw 2026.11.5 release, published on November 17, 2026 and now marked as the latest stable version, lists “Safer updates” among its highlights: a failed Doctor run or a failed Gateway startup now rolls back an update that was already activated. Less than a day later, the project published 2026.10.33, an extended-stable release that its notes call the project’s “current equivalent to LTS.” For a solo operator or a small business that runs one OpenClaw Gateway on a home machine or a small server, the two releases change how much risk a routine update carries and give a second option for how often to take one.

The gap the rollback change closes

Pull request 197851, merged on November 13, describes two cases in which a bad release could stay installed after the updater had switched to it. In the first, the updater recorded the database schema versions from before the update only under certain conditions. Without that record, it could not prove that rolling back was safe, so it reported rollback-state-unverified and left the new release in place. The pull request now reads that baseline for every SQLite-backed install. PostgreSQL installs keep the earlier behavior for now.

In the second case, an update that did not restart a background service never actually started the new release before declaring success. A new step, activated-gateway-startup, now boots the activated release once on the real state, with channels, model providers, cron and file watchers turned off, and waits up to two minutes for the Gateway’s /readyz check. If the Gateway does not become ready, the update fails and the existing rollback path runs. The step is skipped when a running Gateway already owns the state, when the profile points at a remote Gateway, or when the Gateway serves TLS.

The pull request includes test results from isolated installs with deliberately broken releases. Before the change, a release that crashed the Gateway at boot left the install on the broken version with the Gateway down. After the change, the same fault was detected in 12.4 seconds and the install was rolled back to the previous version with the Gateway healthy. A clean update spent 4.5 seconds on the new boot check.

A second fix in the same highlight, pull request 193272, addresses Linux servers where OpenClaw is installed globally by root and the Gateway service runs as a different user. According to the pull request, a failed update could leave the restored package unreadable to that service, so the old version could not start after the rollback. Restored package files now keep their normal read permissions.

What rollback restores, and what it does not

The rollback and recovery documentation sets out the conditions. Automatic rollback runs only when the database schema versions still match their values from before the update and the config file still matches what the new version’s Doctor wrote. When both checks pass, the updater stops the new version and restores the previous package, command shim, service definition and the exact earlier config bytes, then checks the restarted Gateway’s health, plugins, channels and /readyz again. Edits an operator makes to the config after activation block the config restore.

The same page states that downgrading a package does not reverse config or database migrations, and that the automatic pre-update config copy is not a full-state backup. Its recommended step before a significant update is an explicit, verified archive:

openclaw backup create --output ~/Backups/openclaw --verify

The documentation warns that the archive can contain credentials, auth profiles and channel state, and should be stored with owner-only permissions. It also recommends running openclaw update --dry-run first and reading any preflight check it names.

A slower line: extended-stable 2026.10.33

The 2026.10.33 notes describe the release as gateway-only: OpenClaw from the end of October 2026, plus critical security updates, reliability and performance fixes, and selected features such as new model support. It ships the core npm package, the matching official npm plugins and the Gateway Docker images. Native app releases are not part of it. The previous release on this line was 2026.9.37, published on November 10 from the September code base.

The highlights carried into 2026.10.33 include replies that survive more restart and reconnect paths on Telegram, WhatsApp and Signal, automations that can react to polled conditions and MCP events, installed skills that agents can search and read on demand instead of loading all of them into the prompt, and a Side chat that stays private to its viewer.

The release channels documentation lists four channels: stable, extended-stable, beta and dev. It recommends stable for most users. Extended-stable is package-only, so a Git checkout cannot use it, and it never applies automatically: the Gateway can show an update hint, but installation happens only when the operator runs it. The switch is one command:

openclaw update --channel extended-stable

The documentation says the updater verifies the exact package selected for that channel and stops on a verification error rather than falling back to the stable, beta or dev release.

Which line fits a small operation

The trade is between features and change rate. Stable 2026.11.5 has the new rollback step, the Telegram widgets covered in this site’s report on the 2026.11.5 beta, and a listed breaking change: third-party harnesses and plugin RPC handlers must adopt a new session control interface, while bundled ones are already migrated. An operator who depends on a third-party plugin may want to confirm that plugin supports 2026.11.5 before updating. Extended-stable trails by about a month and is meant for Gateways that should change only when the operator chooses.

For a Gateway that runs scheduled jobs overnight or answers a business chat, an update that fails and leaves the Gateway down is the main cost the rollback change addresses. Earlier coverage of update safety, including the Node runtime floor and update guardrails, describes the checks that run before a release is activated. The 2026.11.5 change adds a check after activation.

Checklist before the next update

  • Create a verified backup with openclaw backup create --verify and store it with owner-only permissions.
  • Run openclaw update --dry-run and resolve any named preflight check.
  • Decide between stable and extended-stable, and set the channel with openclaw update --channel.
  • Check that any third-party harness or plugin supports 2026.11.5 before moving to stable.
  • Avoid editing the config while an update is running, since post-activation edits block the automatic config restore.
  • Keep every recovery location the update report names until the new version is verified.

Operators setting up a new Gateway can start with the OpenClaw installation guide. The AI agent harness guide compares how other agent systems handle releases and updates.

Sources