OpenClaw says the wait is almost over, but v2026.8.1 is still beta

OpenClaw’s official account posted a one-line status on August 30, 2026, at 00:51 UTC: "The wait is almost over!"

That sentence is the whole post, aside from a link. It does not name v2026.8.1, a ship clock, or a stable tag. Read it as an official teaser, not as a general-availability drop.

The public releases index still shows the 2026.8.1 line as pre-release only. Operators who have been waiting on that line should not change production pins until a non-beta tag actually appears.

The index has not promoted 8.1

The OpenClaw releases page currently accounts for 30 versions: 9 labeled Stable and 21 labeled Pre-release. In that catalog:

v2026.8.1-beta.3 is a pre-release dated August 24, 2026.
v2026.8.1-beta.2 is a pre-release dated August 15, 2026.
No v2026.8.1 entry without a beta suffix is listed.
v2026.9.1-beta.1, dated August 28, 2026, is marked the latest pre-release — already newer than the newest 8.1 beta.
The top-listed Stable build is v2026.7.1-2, dated August 3, 2026.

A social-status "almost over" does not override those labels. If you need a green install path, you are still on the 7.1.x stables.

What the 8.1 betas actually contain

The index gives two 8.1 highlight blocks. They are the features you can cite today, and they are still beta-tagged.

v2026.8.1-beta.2 (August 15, 2026) highlights secret egress host binding: bind each shared-store secret to exact HTTPS destination hosts across CLI, Gateway RPC, and Control UI so unbound sentinel substitution fails closed.

v2026.8.1-beta.3 (August 24, 2026) highlights GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support across OpenClaw and the Codex runtime. It also notes that Control UI first-run setup now continues verified model setup into Custodian.

Those notes are why the 8.1 line is interesting for agent operators: tighter secret-to-host binding, and named GPT-5.6 reasoning variants on both OpenClaw and Codex. They are not why you should upgrade a fleet tonight.

GPT-5.6 itself is not new in 8.1. The v2026.7.1 stable notes (July 13, 2026) already describe expanded model and provider support including GPT-5.6, alongside Control UI and onboarding overhauls and updates to the official iOS, Android, and macOS apps. The 8.1-beta.3 work is additional reasoning support (Sol, Terra, Luna, Ultra), not the first appearance of the GPT-5.6 runtime.

9.1 is already in beta while 8.1 is not stable

Four days after 8.1-beta.3, the index added v2026.9.1-beta.1 (August 28, 2026). It is marked Latest Pre-release. Its listed highlight is Gateway restart recovery: preserve admitted turns across repeated Gateway restarts so restart-safe runs continue through each checkpoint and deliver their final response.

That ordering is the practical tell. The project is already publishing a 9.1 pre-release while 8.1 has not been marked Stable. Whatever "the wait" refers to, the catalog does not show a completed 8.1 GA.

Stable remains 2026.7.1-2

openclaw 2026.7.1-2 (August 3, 2026, Stable) is a correction release: accept singleton-array metadata from newer npm clients so tracked official plugins can install and update to correction releases (#108336).

v2026.7.1-1 (August 3, 2026, Stable) keeps app-server turns running after delivered progress messages so GPT/Codex reaches its authoritative terminal response instead of stopping mid-turn (#106961, #108487).

Earlier stables on the same page include v2026.7.1 (July 13, 2026) and several 2026.6.x builds. v2026.6.34 and v2026.6.33 are both listed as Stable with August 8, 2026 dates — later calendar dates than 7.1-2, lower version numbers. Use version labels, not calendar order, when you pick a pin.

A separate 2026.7.2 line appears only as pre-releases on this page, up through v2026.7.2-beta.7. Those notes talk about state safety and recovery, including a quarantine store that survives primary-database damage, crash-recoverable SQLite snapshots, and remote coding sessions. There is no 2026.7.2 stable on the index. Do not mix 7.2 beta highlights into an 8.1 upgrade story.

How operators should read the teaser

The @openclaw post supports one claim: on August 30, 2026, the project account said the wait is almost over. The post does not name a version, describe remaining release work, or point to a stable tag.

Until the releases index shows a v2026.8.1 row labeled Stable, treat 8.1 as unfinished:

Secret egress host binding is documented on 8.1-beta.2.
GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support is documented on 8.1-beta.3.
Gateway restart recovery is documented on 9.1-beta.1, which is a different line.
The current top-listed stable remains 2026.7.1-2.

Fail-closed secret binding and new reasoning runtimes will change runtime behavior. Put them on isolated evaluation hosts, not on the agents that already work on 7.1-2.

Next step: Check the OpenClaw releases index for a v2026.8.1 entry labeled Stable. If you still only see beta.2 and beta.3, keep production on v2026.7.1-2 and read the 8.1-beta.3 and 8.1-beta.2 notes before you trial those builds in isolation.