v2026.8.1-beta.2 is a channel and session story. The official source describes a channel, client, interface, or browser change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.
The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.
Channel
Pre-Release
Primary signals
Secret egress host binding; GPT-5.6 Ultra and runtime switching; Channel plugin ingress monitors
Publication date
2026-08-15
Follow the message path
Secret egress host binding
Evidence from the release. bind each shared-store secret to exact HTTPS destination hosts across CLI, Gateway RPC, and Control UI so unbound sentinel substitution fails closed before plaintext egress.
Operator reading. The useful evidence for Secret egress host binding is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.
GPT-5.6 Ultra and runtime switching
Evidence from the release. support Sol, Terra, and Luna across OpenClaw and Codex engines; keep model, runtime, and thinking selection atomic through /model and fallback; and add live matrix coverage for both harnesses.
Operator reading. Use GPT-5.6 Ultra and runtime switching as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.
Channel plugin ingress monitors
Evidence from the release. add a shared plugin SDK monitor for durable admission, polling, pruning, claim identity validation, adoption handoff, and shutdown, and migrate IRC, Synology Chat, and Google Chat to the shared lifecycle.
Operator reading. The operator question around Channel plugin ingress monitors is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.
SQLite snapshots
Evidence from the release. add openclaw backup sqlite create|list|verify|restore for compact, verified global and per-agent database artifacts with fresh-target-only restore.
Operator reading. Test SQLite snapshots at the edges of the interface: clean start, reload, reconnect, and a refused or unavailable action. Keep the final screen and error message with the release note.
The less visible details
macOS app profiles
isolate named app instances across state, preferences, Keychain, Gateway services, and duplicate-instance ownership while keeping host-global login and node services untouched.
For macOS app profiles, inspect state rather than only the new control. Repeat the flow after reload and reconnect, and note the session, pending action, URL, and visible error.
Release validation
defer beta candidate Parallels smoke to postpublish release:beta-smoke by default, keep stable/full prepublish coverage, and bound nested release workflow monitors with explicit job timeouts.
For Release validation, inspect state rather than only the new control. Repeat the flow after reload and reconnect, and note the session, pending action, URL, and visible error.
Codex subagent fan-out
settle successful terminal yields immediately and preserve requester ownership so completed children reliably resume their parent.
A catalog label for Codex subagent fan-out is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.
Test this release without widening the boundary
- Note the current version, host, provider, and workspace before exercising Secret egress host binding.
- Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
- Send one harmless message through the named account and save the account, thread, and sender identifiers.
- Compare the transcript before and after reconnect, including delivery state and any visible error.
- Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.
openclaw --version
openclaw gateway status
openclaw security audit
Record what the release actually changed
Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.
Corrections worth replaying
Codex subagent fan-out. settle successful terminal yields immediately and preserve requester ownership so completed children reliably resume their parent. Keep the reproduction and the post-fix result together in the acceptance record.
Control UI session companion. load bounded visible session context before answering, keep unavailable questions retryable, and prevent private companion reference wrappers from appearing as answers. Fixes #120746. Record the failure that this correction addresses before declaring the upgrade complete.
Use the complete OpenClaw v2026.8.1-beta.2 release notes for the exact change list, then cross-check the official release index and the channel routing guide before acting.
Reference Trail
Sources and further reading
- complete OpenClaw v2026.8.1-beta.2 release notesgithub.com
- official release indexgithub.com
- channel routing guidedocs.openclaw.ai