OpenClaw 2026.9.5 keeps the Gateway up while it updates

OpenClaw 2026.9.5 is on GitHub and npm. The official post listed atomic updates, plugin hot reload, conversation sharing, expanded GPT Live, shared browser pages, conversation archiving, and specialist-agent setup. The docs list the same features. Jason Sy's blog is the why: after 2.0, a failed update could take the only agent you had offline.

The tagged notes list 4,179 pull requests, 64 direct commits, and 503 contributors. Those counts are the project's. The X post said 502 contributors. The GitHub tag is 503.

If you stayed on 2026.8.1 because updates were scary, this is the cut that tries to fix that path.

Atomic updates

OpenClaw keeps the existing Gateway running while it prepares the next version. If the update fails, it rolls back to the last working configuration. It is supposed to leave you with a working agent that can help diagnose the failure.

Sy is explicit that this is not "completely fixed." Report the issue and use Discord if it still breaks. There is a new issue-reporting button for updates.

Docs put the same idea under Updates and Maintenance: atomic updates check the next version before switching over on supported paths. Conversation archiving compresses older history you can reopen later, with storage controls in Settings.

If openclaw update used to strand you after 2.0, try again on a machine you can restore. It is not a promise that every config permutation is safe.

Plugins, sharing, specialists

Install or reload supported plugins while the Gateway keeps running. Teammates can get read-only access to selected conversations.

Setup can help you create a specialist or a small team, pick an avatar, and get connected. Experimental room teams let several agents take part in one conversation.

GPT Live, browsers, Mac

GPT Live reaches Talk, meetings, and phone calls. You can share a page in a local managed browser with your agent and use computer controls on supported local or cloud desktops.

The Mac app now opens the Web experience by default, with an experimental Native option.

How to update

openclaw update. Create a verified backup first. npm latest and beta are 2026.9.5. extended-stable is 2026.6.35. Engines are still >=24.16.0 <25 || >=26.1.0. Tagged LICENSE is MIT, Copyright 2026 OpenClaw Foundation. GitHub's license API still says NOASSERTION.

A linux-stable GitHub prerelease on the same day points at 2026.9.5 Linux companion builds. That is the Linux app channel, not a second product version.

Take 2026.9.5 for the update path: Gateway stays up, rollback if the next cut is bad. If that holds on your config, you get plugins, Live, and sharing as extras. If it does not, you should still have an agent left to tell you why.