OpenClaw v2026.4.20-beta.1: Onboard/wizard, operator field notes

The source record for v2026.4.20-beta.1 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 / Onboard/wizard

Source signal. restyle the setup security disclaimer with a single yellow warning banner, section headings and bulleted checklists, and un-dim the note body so key guidance is easy to scan; add a loading spinner during the initial model catalog load so the wizard no longer goes blank while it runs; add an "API key" placeholder to provider API key prompts.

Read Onboard/wizard as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

02 / Agents/prompts

Source signal. strengthen the default system prompt and OpenAI GPT-5 overlay with clearer completion bias, live-state checks, weak-result recovery, and verification-before-final guidance.

Check Agents/prompts with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

03 / Models/costs

Source signal. support tiered model pricing from cached catalogs and configured models, and include bundled Moonshot Kimi K2.6/K2.5 cost estimates for token-usage reports.

Models/costs changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

04 / Exec/YOLO

Source signal. stop rejecting gateway-host exec in security=full plus ask=off mode via the Python/Node script preflight hardening path, so promptless YOLO exec once again runs direct interpreter stdin and heredoc forms such as node <<'NODE' ... NODE.

Before widening access for Exec/YOLO, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

The details that affect a runbook

OpenAI Codex

normalize legacy openai-completions transport overrides on default OpenAI/Codex and GitHub Copilot-compatible hosts back to the native Codex Responses transport while leaving custom proxies untouched.

The safe reading of OpenAI Codex is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Onboard/wizard.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Exercise the named capability with a non-sensitive prompt, including the fallback or refusal result if it occurs.
4. Force a timeout or provider fallback in a disposable session and verify that no side effect is repeated.
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 security audit

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.

Regression cases from the source

Exec/YOLO. stop rejecting gateway-host exec in security=full plus ask=off mode via the Python/Node script preflight hardening path, so promptless YOLO exec once again runs direct interpreter stdin and heredoc forms such as node <<'NODE' ... NODE. Treat the fix as a boundary condition and retain the source wording beside your local result.

OpenAI Codex. normalize legacy openai-completions transport overrides on default OpenAI/Codex and GitHub Copilot-compatible hosts back to the native Codex Responses transport while leaving custom proxies untouched. Keep the reproduction and the post-fix result together in the acceptance record.

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