OpenClaw v2026.8.1-beta.3: Puppeteer-compatible CDP relay support, operator field notes

The source record for v2026.8.1-beta.3 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

A small field test

01 / GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support

Source signal. GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support across OpenClaw and the Codex runtime.

The safe reading of GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

02 / Control UI first-run setup now continues verified model

Source signal. Control UI first-run setup now continues verified model setup into Custodian and optional channel setup.

Use Control UI first-run setup now continues verified model 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.

03 / Puppeteer-compatible CDP relay support for paired Chrome

Source signal. Puppeteer-compatible CDP relay support for paired Chrome sessions.

Measure Puppeteer-compatible CDP relay support for paired Chrome after a fresh session and after a reconnect. The record should say what was retained, what was intentionally absent, and which identity requested the recall.

04 / Explicit external Gateway lifecycle supervision

Source signal. Explicit external Gateway lifecycle supervision with verified restart handoff.

Keep Explicit external Gateway lifecycle supervision measurable: name the input, expected output, failure signal, and operator who approved the test before calling the change ready.

The details that affect a runbook

Compact, verified SQLite backup and fresh-target restore

Compact, verified SQLite backup and fresh-target restore commands.

The promise in Compact, verified SQLite backup and fresh-target restore is only useful if the old state returns. Take a verified backup, interrupt a candidate update, and inspect both the retained package and the service.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for GPT-5.6 Sol, Terra, Luna, and Ultra reasoning support.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw models

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

This page is a practical reading of the v2026.8.1-beta.3 source record; the release index and model provider reference remain the references to use for migrations and support boundaries.