← All articles

OpenClaw 2026.11.5: Restart Recovery and Plugin Upgrade Checks

OpenClaw 2026.11.5 improves restart recovery and update rollback. Check the breaking plugin change, running Gateway and scheduled work before upgrading.

OpenClaw 2026.11.5 is an important upgrade for teams running persistent agents or custom plugins. The November 17 stable release improves restart recovery and update rollback, but also changes how third-party integrations control sessions. Review that compatibility boundary before updating a business workflow. Official 11.5 release

This guide treats the preceding 11.4 release and 11.5 as one upgrade review. The earlier patch addresses skipped buffered Signal messages, replies lost after settings reloads and damaged memory or configuration recovery copies. If you skipped that version, include reconnect and reload checks in the same maintenance window.

What changes for a running agent?

Queued messages, send permissions and final conversation writes now survive Gateway restarts. Failed Doctor or Gateway startup checks can roll back an activated update. The release also fixes scheduled account selection, retry deadlines and late scheduler wakeups, and rechecks access to owner-private memory before queued automation starts. Recovery and automation changes

My practical recommendation is to test the interruption boundary that matters to your business. For example, run an agent that prepares an internal report in a test workspace. Record its request, stop point and eventual result. Confirm that the conversation remains coherent after recovery and that a queued action still needs the right authorization.

A recovered conversation does not establish that an external email, payment or database write happened exactly once. Check the destination before retrying a consequential action, and use the destination system’s duplicate protection where available. This is deployment advice, not an additional guarantee from the release.

Which plugin change can break an upgrade?

Third-party harnesses must register active runs by session inside the host’s runAttempt callback and retain the returned cleanup function. Plugin RPC handlers must use authorized Gateway dispatch instead of chatAbortControllers or chatQueuedTurns. Start-owner observations now use startDeadlineAtMs, replacing expiresAtMs. Bundled consumers have been migrated. Breaking-change notice

If you maintain an integration, search its session-management code for those interfaces before scheduling the update. Ask its maintainer for compatibility evidence if you cannot inspect the implementation. Loading successfully is only the first check: exercise start, cancellation, queued work and cleanup in an isolated session.

For a failed test, keep the previous working deployment available and capture the smallest reproducible case. Avoid solving a permission failure by granting the plugin broader access. The intended result is the same authorized workflow on the new lifecycle.

How should you update OpenClaw?

The official documentation recommends the managed updater, which checks the installation while the existing Gateway serves work, then activates and verifies the update. A global package update can target a different Node installation from the one used by the service. A shell version alone therefore does not prove the running Gateway changed. Updating documentation

Use this sequence for a controlled maintenance window:

  1. Identify the deployment. Note the host, installation method, running version, enabled plugins and the workflows you must preserve. Tell affected users when testing will happen.
  2. Prepare recovery. Follow the official backup guide, protect the backup and verify that you know how to restore it. Record the previous working configuration.
  3. Preview the update. Run openclaw update --dry-run and review the planned target and any warnings. Resolve compatibility questions before activation.
  4. Run the managed update. Use openclaw update for the documented installation path. Investigate failed checks rather than immediately repeating the operation.
  5. Inspect the service. Review openclaw gateway status, openclaw status and openclaw doctor. Compare the serving Gateway with the intended installation.
  6. Verify useful work. Complete a harmless request through the channel your users actually use. Check its result outside the agent when it writes to another system.

The managed updater already restarts and verifies the Gateway on success; an extra manual restart is not a routine requirement. Automatic rollback is also not a substitute for recovering all application state from a backup. Update verification and recovery

What should your acceptance check include?

Before returning a production agent to normal use, keep a short evidence record:

Workflow Evidence to keep
Conversation Request and final reply remain associated with the correct session
Permissions An unauthorized test stays blocked; an authorized test still works
Scheduled work A harmless job runs under the intended account and produces the expected result
Custom integration Start, cancellation and cleanup behave correctly without orphaned work
Recovery The known backup and previous working deployment remain available

These are recommended acceptance checks, not claims that FindMilan has tested every deployment or plugin. Start with a small pilot if the agent handles customer communication or business records. Expand only when the evidence matches the workflow you intend to automate.

If you want help reviewing your installation, Milan’s OpenClaw setup and upgrade support can help you scope the migration and verification work. The agent setup project shows the broader approach to connecting models, tools and operational checks.

Frequently asked questions

What is the main change in OpenClaw 2026.11.5?

The release improves conversation recovery across Gateway restarts and rollback after failed update activation checks.

Do third-party plugins need review?

Yes. Third-party harnesses and plugins that manage sessions must check the breaking session-control changes before upgrading.

Does update rollback replace a backup?

No. Keep a verified backup and a recovery plan for your installation and state.

How should I verify the upgrade?

Check the running Gateway, then test a real conversation, permissions, scheduled work and any custom plugins you use.

FAQ

Frequently asked questions

What is the main change in OpenClaw 2026.11.5?

The release improves conversation recovery across Gateway restarts and rollback after failed update activation checks.

Do third-party plugins need review?

Yes. Third-party harnesses and plugins that manage sessions must check the breaking session-control changes before upgrading.

Does update rollback replace a backup?

No. Keep a verified backup and a recovery plan for your installation and state.

How should I verify the upgrade?

Check the running Gateway, then test a real conversation, permissions, scheduled work and any custom plugins you use.

Need help with OpenClaw setup and upgrade support?

Turn the idea into a working system.