AI AgentsAugust 15, 2026

OpenClaw’s next release is already on the beta tag

By AgentRiot Editorial

2026.8.1-beta.1 landed on npm August 10 without GitHub release notes. Official docs still feature July’s 2026.7.1, while `main` keeps absorbing a huge Unreleased changelog.

OpenClaw release beta AI agents gateway

OpenClaw did not go dark. The reader-facing story did.

If you watch the curated release notes, the last product write-up is still v2026.7.1 from 13 July 2026. That is the cut that overhauled Control UI and onboarding, pushed official iOS, Android, and macOS apps, and expanded GPT-5.6, Hy3, and Muse Spark 1.1 support. After that page, the docs go quiet.

The package registry tells a different story. As of 15 August 2026, npm’s latest tag is still 2026.7.1-2. The beta tag is 2026.8.1-beta.1, published 10 August 2026. GitHub has the matching tag, signed by Vincent Koc. It does not have a GitHub Releases page or a ## 2026.8 changelog heading. The next version exists as a tagged npm beta, not as a documented release.

That gap is what people are reading as “no update.”

What is actually current

OpenClaw is shipping three channels at once. They are easy to mix up.

Channel	Identifier	Where it lives	Dated
Reader-facing notes	2026.7.1	docs.openclaw.ai/releases	13 July 2026
npm `latest`	2026.7.1-2	npmjs.com/package/openclaw	GitHub release 4 August 2026
npm `beta`	2026.8.1-beta.1	npm dist-tag `beta`	10 August 2026
npm `extended-stable`	2026.6.34	GitHub release 8 August 2026	hardening-only

2026.7.1-2 is a one-fix correction: accept singleton-array metadata from newer npm clients so official plugins can install correction releases (#108336). 2026.6.34 is an extended-stable hardening train: safer browser and network boundaries, more resilient provider runs, and dependency patches. Neither is the next product story.

The next product story is the 2026.7.2 beta line, then the August tag that replaced it on npm.

The parked 2026.7.2 train

OpenClaw published seven 2026.7.2 betas. The last GitHub pre-release is v2026.7.2-beta.7 on 2 August 2026. That note is not a small patch list. It is a second major cut after July:

crash-durable SQLite snapshots, a quarantine store, and schema-upgrade data-loss rejection
durable ingress drain and dead-letter recovery across Telegram, Signal, Slack, and other channels
session rewind and branching on web and native apps
ticketed MCP Apps that can be pinned to dashboards
structured questions and approvals across Control UI, channels, and native apps
Teams, Zoom, and Google Meet guests with durable transcripts
a phone-proxied Wear OS companion

That is operator infrastructure. It is also a lot of surface to bless as stable. After beta.7, GitHub stopped cutting 2026.7.2 pre-releases. Eight days later the npm beta tag jumped to 2026.8.1-beta.1.

The August tag’s annotated message is only OpenClaw 2026.8.1-beta.1. The pointed commit is fix(release): backport dependency evidence runner. There is no public release body to explain what moved from the 7.2 train into 8.1, or what got held back. Treat the npm beta as a real published artifact, not as a finished narrative.

The Unreleased pile is the actual status page

Open the current CHANGELOG.md on main and the first heading is still ## Unreleased. On 15 August 2026 that section was about 89,000 characters and 387 bullets. There is no 2026.8 heading in the file.

The unreleased work is not filler. It includes secret egress host binding, macOS app-profile isolation, Control UI update recovery after a Gateway restart, SQLite snapshot backup commands, GPT-5.6 Ultra runtime switching, Fish Audio speech, ClickClack setup, Buzz channel fidelity, Skill Workshop approvals, and an OPENCLAW_SUPERVISOR_MODE=external contract for lifecycle owners. Those lines sit above the published 2026.7.1 notes, not inside them.

main was still receiving merges on 15 August 2026: session maintenance, Gateway pairing tests, Control UI connect-error overhead, truthful memory-index outcomes, and preserving node workspaces across restarts. The repository is not waiting. The release process is.

GitHub compare against older tags reports a huge diverged history. That number is a bad headline. CalVer tags, beta lines, and long-lived branches make compare counts lie. The changelog and the npm tags are the cleaner evidence.

Why it looks stalled

On 14 August 2026 the official @openclaw account posted: “Thanks for being patient with us while we finish this properly and make sure the release is worth the wait.” Two days earlier they pointed people at ClawCast episode 7, an unfiltered Q&A with founder @steipete about the upcoming release.

That matches the artifact trail. A large 7.2 beta already exists. An 8.1 beta is on npm. The docs still sell July. The changelog is still Unreleased. The public request is patience, not a date.

The honest reading is narrower than “they vanished” and broader than “the next version is done.” OpenClaw is holding the reader-facing cut until the release machinery, native apps, and operator paths can carry the pile. The 7.2 note already spends as much space on recovery, delivery, and authorization as it does on features. The Unreleased section keeps adding the same kind of work.

If you run production Gateways, that is the right kind of delay. It is still a communication gap. A tagged npm beta with no GitHub release page will keep looking like silence to anyone who only reads docs or Releases.

What to run

Stable install is unchanged:

npm install -g openclaw@latest

The project installer is still curl -fsSL https://openclaw.ai/install.sh | bash on macOS, Linux, and WSL2. Official docs also cover Docker, Nix, and release channels.

The current beta package is:

npm install -g openclaw@beta

That currently resolves to 2026.8.1-beta.1. It is a pre-release. Do not treat it as the documented 2026.7.1 line, and do not assume GitHub Releases will explain it.

Sources

Accessed 15 August 2026.