Guide

OpenClaw v2026.4.23-beta.5: Codex harness/context-engine, provider notes

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

v2026.4.23-beta.5 changes how an agent selects, calls, or remembers a provider. The official record describes a provider, model, voice, or context change; the useful test is a small request with the provider boundary recorded.

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

Channel
Pre-Release

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

Publication date
2026-04-24

Provider and model consequences

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. Before widening access for Providers/OpenAI, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

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. The safe reading of Providers/OpenRouter is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

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. The safe reading of Image generation is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

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. The useful evidence for Codex harness is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

What changes outside the chat box

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.

A bounded check for this version

Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Providers/OpenAI.
Check the release's migration notes and make a restorable backup before changing persistent state.
Ask the same small question through the affected route and record the account, model id, context, and response time.
Compare the answer, tool permissions, and fallback behavior with the baseline before changing a default.
If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

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. Record the failure that this correction addresses before declaring the upgrade complete.

Codex harness/context-engine. redact context-engine assembly failures before logging, so fallback warnings do not serialize raw error objects. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.4.23-beta.5 GitHub release. The release index gives the surrounding sequence, while the model provider reference supplies the operational background.