How do I update OpenClaw to the latest version?

Re-run the install script: on macOS and Linux use `curl -fsSL https://openclaw.ai/install.sh | bash`, on Windows PowerShell use `iwr -useb https://openclaw.ai/install.ps1 | iex`. If you installed via Homebrew, npm, or Scoop, update through that package manager instead. After updating, verify with `openclaw --version` and restart the gateway.

How do I check which version of OpenClaw I have installed?

Run `openclaw --version` in your terminal. The output prints the full calendar version string, for example `openclaw v2026.2.26`. You can also find the version in the footer of the OpenClaw Control UI dashboard.

Where can I read OpenClaw release notes?

The canonical source is the GitHub releases page at github.com/openclaw/openclaw/releases, where every tagged version has a full changelog. OpenClaw Launch also publishes a /changelog and a /news page summarizing notable releases.

What was added in the latest notable OpenClaw release?

OpenClaw v2026.2.26 (February 27, 2026) introduced External Secrets Management with audit/configure/apply/reload CLI commands, first-class ACP thread-bound agent runtimes, an agent routing CLI (openclaw agents bindings/bind/unbind), and Android device capabilities — all contributed by 48 developers.

← Home

Reference

OpenClaw Releases & Changelog — Latest Version, What's New & How to Update

OpenClaw ships releases frequently under a calendar-based version scheme. This page explains how versioning works, how to check what you have installed, how to update on any platform, and where to read the full release notes for every build.

How OpenClaw Versioning Works

OpenClaw uses calendar-style version numbers in the form v<year>.<month>.<day> — for example v2026.2.26 for a release published on February 26, 2026. There is no major/minor/patch hierarchy. Every tagged release on the GitHub releases page corresponds to a specific calendar date, so you can immediately tell how recent a build is just from the version string.

This scheme makes it straightforward to answer "how out of date am I?" — if today is 2026-06-25 and you are running v2026.2.26, you know you are roughly four months behind the current line and should review the release notes between that date and today before updating in a production environment.

Patch releases on the same day are rare. When they occur they increment the day segment (e.g. v2026.2.26.1) or appear as a follow-up release tagged the next calendar day.

How to Check Your Installed Version

Run the following command in any terminal where OpenClaw is available:

openclaw --version

The output prints the full version string, for example openclaw v2026.2.26. If the command is not found, OpenClaw is either not installed or not on your PATH. See the install guide for setup instructions.

You can also check the version from inside the OpenClaw Control UI. Open your gateway dashboard and look for the version badge in the footer or the About section.

How to Update OpenClaw

The recommended way to update is to re-run the same install script you used for the initial installation. The script is idempotent: it detects the existing installation, downloads the latest release, and replaces the binary in place.

macOS and Linux

Open a terminal and run:

curl -fsSL https://openclaw.ai/install.sh | bash

The script places the binary in /usr/local/bin/openclaw by default. If you installed to a custom path, pass OPENCLAW_INSTALL_DIR as an environment variable before piping to bash.

After the script completes, verify the update with openclaw --version and restart the gateway if it was already running: openclaw gateway restart.

Windows (PowerShell)

Open PowerShell as Administrator and run:

iwr -useb https://openclaw.ai/install.ps1 | iex

If your execution policy blocks the script, run Set-ExecutionPolicy RemoteSigned -Scope CurrentUser first, then re-run the install command. See the Windows setup guide for more detail.

Package Managers

If you installed via a package manager, update through that path instead so it can track the version in its manifest:

# Homebrew (macOS / Linux)
brew upgrade openclaw

# npm global
npm install -g openclaw@latest

# Windows Scoop
scoop update openclaw

After any package-manager update, confirm the version and restart the gateway the same way as above.

Where to Read Release Notes

There are several places to follow OpenClaw releases:

The official GitHub releases page is the canonical source. Every tagged version has a full changelog entry listing new features, fixes, and security patches.
The OpenClaw Launch changelog tracks how managed instances on this platform are updated, including image pins and rollout timing.
The OpenClaw Launch news page summarizes notable releases with context on what each change means for users.

If you run a managed instance on OpenClaw Launch, you do not need to monitor releases manually. Instances are kept on a tested, pinned image and updated as part of the regular platform refresh cycle — so you get new features and security patches without having to run the install script yourself.

Recent Notable Release: v2026.2.26

OpenClaw v2026.2.26, published February 27, 2026, is a significant feature release from 48 contributors. The four headline additions are:

External Secrets Management workflow — a complete openclaw secrets CLI with audit, configure, apply, and reload subcommands. This lets you rotate or apply API keys and credentials at runtime without restarting the gateway.
ACP (Agent Communication Protocol) thread-bound agent runtimes as first-class citizens. Agents can now be bound to specific conversation threads with full dispatch integration and lifecycle controls, enabling more structured multi-agent workflows.
Agent routing CLI — new openclaw agents bindings, bind, and unbind commands for account-scoped agent route management without editing config files directly.
Android device capabilities — status and info node commands plus a notifications listing feature, bringing the Android experience closer to the desktop.

The release also shipped multiple security fixes including node execution approval enforcement, gateway authentication path validation, device pairing metadata pinning, workspace boundary symlink validation, Teams media fetch SSRF guarding, and Twilio webhook replay protection.

The full changelog is at github.com/openclaw/openclaw/releases/tag/v2026.2.26.

Managed Instances on OpenClaw Launch

OpenClaw Launch keeps every managed instance on a verified, tested image pin. When a new release is validated, the platform rolls it out to instances automatically — you do not have to run the install script, restart services, or watch the GitHub releases page. Security patches reach your instance the same way, without any manual steps on your part.

If you prefer to stay on a specific version, contact support and we can discuss a pinned image for your instance.