OpenClaw Adds Atomic Updates and Guided Agent Teams in v2026.9.5

OpenClaw has released v2026.9.5, adding a guided route to create specialist agent teams while changing how the platform is updated, extended and shared. The release is aimed at making routine setup and maintenance less interruptive.

The update introduces Atomic Updates, which check the next version before OpenClaw switches over. It also allows plugins to be installed without restarting the Gateway, the service that runs the platform. Together, those changes target two moments that can interrupt an active installation: upgrading software and adding functionality.

4,179Pull requests

OpenClaw says the release includes 4,179 pull requests.

64Direct commits

The release also includes 64 direct commits.

502Contributing accounts

OpenClaw credits contributions from 502 accounts.

The setup flow can now create either one specialist or a four-agent team made up of a chief of staff, researcher, writer and reviewer. The web Control UI can also create agents from roles or team presets, presenting a proposal for approval before it creates anything.

New-agent setup can generate and save an avatar, although users can keep an emoji instead. For fresh OpenAI and ChatGPT/Codex setups with no primary model selected, OpenClaw defaults to Astra when the account offers it; existing model choices stay in place.

Workflows added in the same release

• Conversations can be shared and archived for later review.
• Users can work with an agent on browser pages, while GPT Live is supported in meetings and phone calls.

Docker-hosted Gateways can share workspace and skill files with sandbox shell and browser tools through verified host bind mounts. Named volumes, tmpfs and files stored only in an image remain unsupported, while OpenClaw refuses sources whose container or Docker daemon it cannot verify.

FreeBSD users can now install the command-line interface through system Node and npm. But OpenClaw does not install or control FreeBSD services. The release can simplify setup and upkeep, while service management remains with the system’s operator.