Guide

OpenClaw v2026.4.23-beta.4: Codex harness, recovery notes

April 24, 20264 min readUpdated September 11, 2026By OpenClawBlog Team

v2026.4.23-beta.4 is easiest to understand through failure. The official record describes a provider, model, voice, or context change; the sections below spell out what to save, what to interrupt, and what must remain available afterward.

This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Channel
Pre-Release

Primary signals
Providers/OpenAI; Providers/OpenRouter; Image generation

Publication date
2026-04-24

Failure and recovery path

Providers/OpenAI

Evidence from the release. add image generation and reference-image editing through Codex OAuth, so openai/gpt-image-2 works without an OPENAI_API_KEY. Fixes #70703.

Operator reading. Treat Providers/OpenAI as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Providers/OpenRouter

Evidence from the release. add image generation and reference-image editing through image_generate, so OpenRouter image models work with OPENROUTER_API_KEY. Fixes #55066 via #67668.

Operator reading. Check Providers/OpenRouter 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.

Image generation

Evidence from the release. let agents request provider-supported quality and output format hints, and pass OpenAI-specific background, moderation, compression, and user hints through the image_generate tool.

Operator reading. A catalog label for Image generation is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

Codex harness

Evidence from the release. route native request_user_input prompts back to the originating chat, preserve queued follow-up answers, and honor newer app-server command approval amendment decisions.

Operator reading. Read Codex harness as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

The limits of the recovery promise

Codex harness/context-engine

redact context-engine assembly failures before logging, so fallback warnings do not serialize raw error objects.

Check Codex harness/context-engine 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.

Run the smallest useful rehearsal

Write down the baseline for Providers/OpenAI, including the installed version, host, provider, and workspace.
Confirm what can be restored, then take a verified backup before applying the candidate package.
Use a disposable session to compare the new model or provider with the previous route on one fixed input.
Restore the previous provider setting after the check and retain the measured result beside the release tag.
Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

Codex harness. route native request_user_input prompts back to the originating chat, preserve queued follow-up answers, and honor newer app-server command approval amendment decisions. This is the edge case to include in a regression check, especially when the release is pre-release.

Codex harness/context-engine. redact context-engine assembly failures before logging, so fallback warnings do not serialize raw error objects. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.4.23-beta.4 notes with your test result. Read the official release index for neighboring versions and the model provider reference for configuration limits.