OpenClaw Latest Version: Release Notes and Changelog

OpenClaw crossed 1.17 million weekly npm downloads in early 2026, with 13 releases shipping in March alone. At that cadence, a single skipped update can mean missing security patches, dependency bumps, and plugin API changes that affect running agents. The latest stable build is 2026.5.18, released May 18, 2026, and it focuses on developer tooling, mobile voice, and Gateway performance.

The headline addition is defineToolPlugin, a new API for building typed tool plugins. The surrounding build toolchain now includes scaffolding, validation, and compilation steps that give plugin authors generated manifest metadata, optional tool declarations, and context factories. If you maintain custom skills or integrations, this replaces the older ad-hoc plugin wiring with a structured build pipeline.

Android Talk Mode landed in this release. It routes realtime voice sessions through the Gateway relay, bringing mobile voice interactions to Android at parity with iOS and desktop. For agents that handle voice across platforms, this closes a gap that had persisted for several months.

Gateway restart performance improved through two specific changes. Startup now overlaps logging and plugin-service initialization with channel sidecar loading, cutting the time to ready state. Restart traces also break down costs by category (startup probe, config load, runtime init, resource count) so operators can pinpoint exactly where latency hides.

Telegram and Discord channels received isolated polling lanes. Previously, a slowdown in one channel's message polling could block others. Each channel now polls independently, improving reliability for agents serving users across multiple messaging platforms.

Dependency updates in this release:

• Internal proxy and networking libraries updated to latest patch versions
• Pi packages bumped to 0.75.1
• Minimum Node.js 22 version raised to 22.19

If you're running an older Node.js 22 patch, update Node.js before upgrading OpenClaw.

Docker and Podman users get a new build argument: OPENCLAW_IMAGE_APT_PACKAGES. It replaces OPENCLAW_DOCKER_APT_PACKAGES as the runtime-neutral way to inject extra system packages into container images. The old name still works as a fallback.

QA-Lab expanded with Codex-vs-Pi runtime parity tests, tool fixture coverage reporting, and personal-agent test packs covering approval-denial workflows. These changes primarily affect contributors and CI pipelines, but they also mean fewer regressions reaching the stable channel.

For operators running OpenClaw in production, 2026.5.18 is a solid upgrade target. It doesn't introduce breaking API changes, but the Node.js 22.19 minimum may require a system-level update. Test the upgrade on the beta channel or a staging environment before promoting to your production gateway.

OpenClaw shipped several notable updates before 2026.5.18 landed. Here's what changed in the first half of May.

v2026.5.3 (May 4) introduced the file transfer plugin with four new agent tools: file_fetch, dir_list, dir_fetch, and file_write. These enable binary file operations between paired nodes with a 16 MB per-round-trip ceiling and operator-controlled path policies. Symlink traversal is blocked by default.

The same release unified streaming progress configuration. Instead of separate channel-specific settings, a single streaming.mode: "progress" value now works identically across Discord, Telegram, Slack, Matrix, and Microsoft Teams.

v2026.5.4 (May 5) added Twilio dial-in integration with the realtime Gemini voice bridge for Google Meet sessions. The implementation uses paced audio streaming with backpressure-aware buffering, which handles overlapping speakers more cleanly than the previous approach. Gateway startup also improved here: plugin discovery, runtime data, cron jobs, schema info, sessions, and model metadata now lazy-load rather than initializing all at once.

v2026.5.5 (May 6) delivered over 50 cross-platform bug fixes. A few highlights:

• xAI and Grok models no longer receive incompatible OpenAI-style reasoning effort controls
• LINE channel validation fails early instead of silently blocking misconfigured direct-message policy settings
• Docker containers drop NET_RAW and NET_ADMIN capabilities by default with no-new-privileges enabled
• iOS pairing supports manual ws:// connections for private networks while keeping wss:// for public routes

v2026.5.6 (May 6) was a same-day hotfix that reverted a route migration breaking GPT-5.5 setups using the Codex OAuth plugin path. Quick turnaround on a regression like this is typical of OpenClaw's release process: ship fast, detect fast, fix fast.

Taken together, the first half of May added binary file operations, voice integration, container security hardening, and cross-platform consistency fixes. If you're upgrading from a pre-May build, the changelog covers significant ground. Review the full release history for versions between your current build and 2026.5.18 to catch any breaking changes specific to your setup.

OpenClaw distributes updates through three channels. Picking the right one depends on how much instability you'll accept in exchange for early access to features.

Stable is the default and recommended channel. Builds carry npm dist-tag latest and use version numbers like v2026.5.18. Every stable release goes through beta testing first. The promotion step moves the vetted build to latest without changing the version number, so what you test in beta is exactly what ships to stable. Use this for production agents.

Beta is the testing ground. Builds use npm dist-tag beta with versions like v2026.5.19-beta.2. New features arrive here first, and the OpenClaw team relies on beta feedback to catch issues before promotion. If the beta dist-tag is missing or older than the current stable release, the update flow falls back to latest automatically. Note that macOS app builds may not always have matching beta versions.

Dev tracks the main git branch with npm dist-tag dev. It can contain incomplete features and breaking changes. The official docs warn against using it for production gateways.

Version numbers follow a date-based scheme: YYYY.M.D for stable, with -beta.N or -alpha.N suffixes for pre-release builds. A version like 2026.5.14-beta.2 means the second beta iteration targeting the May 14 stable train.

Switch channels through the built-in updater by specifying the target channel name. Your choice persists in your configuration file. To install a specific version without changing your default channel, pass the exact version tag instead. See the official release notes for current syntax.

Keep your OpenClaw agent files safe across version updates

generous storage workspace storage with MCP access. Files persist through reinstalls, machine migrations, and version upgrades. No credit card required.

Start 14-Day Trial

Run openclaw --version to see your installed build. It returns version numbers for the OpenClaw core, gateway, and runtime. All three should match. If they don't, a partial update may have failed, and you should re-run the update.

The built-in updater can check for available releases without installing them, letting you preview what would change before committing. When you're ready, the updater downloads the latest release on your configured channel, verifies the checksum, installs it, restarts the gateway, and confirms success. A dry-run mode shows exactly what would happen without applying changes.

To roll back to a previous version, install it directly:

npm install -g openclaw@2026.5.16

OpenClaw prompts for confirmation when downgrading. After a rollback, verify configuration compatibility:

openclaw config validate

The built-in diagnostic command validates your entire environment after any version change:

openclaw doctor

It checks Node.js version compatibility, plugin states, configuration syntax, and gateway connectivity. Run it after every upgrade or rollback. This matters especially after a release like 2026.5.18 that bumped the minimum Node.js version to 22.19.

For teams running multiple OpenClaw instances, consider automating version checks. The updater's check mode exits with a non-zero status when updates are available, making it straightforward to integrate into monitoring scripts or scheduled jobs.

OpenClaw preserves configuration and agent state during standard updates. Skills, memory files, session history, and your gateway config carry forward automatically. But version updates sometimes change configuration schemas or deprecate plugin APIs. Skill compatibility is the most common breakage point.

Before updating, back up these directories:

• ~/.openclaw/openclaw.json (gateway configuration)
• ~/.openclaw/memory/ (agent conversation memory)
• ~/.openclaw/sessions/ (session history)
• ~/.openclaw/skills/ (installed skills and data)

A quick cp -r ~/.openclaw ~/.openclaw-backup covers everything. After upgrading, test critical skills with openclaw skills test <skill-name> before routing live traffic through your agent.

For agents that manage files for clients or teams, local disk backups only protect against local failures. If your agent processes documents, stores deliverables, or maintains a knowledge base, consider a cloud storage layer that persists independently of your OpenClaw installation. S3, Google Drive, or a shared workspace platform keeps agent output safe regardless of version changes or machine failures.

Fastio provides 50 GB of free workspace storage with MCP server access for OpenClaw agents. Files are automatically indexed for semantic search when Intelligence is enabled, so your agent can query its own document history with natural language. The free tier includes included credits, 5 workspaces, and requires no credit card. Because agent files live in cloud workspaces rather than ~/.openclaw/, version updates, reinstalls, and machine migrations leave stored data untouched.