OpenClaw v2026.4.11: Tools/video_generate, provider notes

v2026.4.11 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.

This is a stable release line; read the exact record for migrations and fixes before applying it to a live Gateway. 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.

Provider and model consequences

Dreaming/memory-wiki

What changed. add ChatGPT import ingestion plus new Imported Insights and Memory Palace diary subtabs so Dreaming can inspect imported source chats, compiled wiki pages, and full source pages directly from the UI.

Check it with. For Dreaming/memory-wiki, 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.

Control UI/webchat

What changed. render assistant media/reply/voice directives as structured chat bubbles, add the [embed ...] rich output tag, and gate external embed URLs behind config.

Check it with. Control UI/webchat changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Tools/video_generate

What changed. add URL-only generated asset delivery, typed providerOptions, reference audio inputs, per-asset role hints, adaptive aspect-ratio support, and a higher image-input cap so video providers can expose richer generation modes without forcing large files into memory.

Check it with. The operator question around Tools/video_generate is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

OpenAI/Codex OAuth

What changed. stop rewriting the upstream authorize URL scopes so new Codex sign-ins do not fail with invalid_scope before returning an authorization code.

Check it with. The useful evidence for OpenAI/Codex OAuth 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

Audio transcription

disable pinned DNS only for OpenAI-compatible multipart requests, while still validating hostnames, so OpenAI, Groq, and Mistral transcription works again without weakening other request paths.

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

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Dreaming/memory-wiki.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Ask the same small question through the affected route and record the account, model id, context, and response time.
4. Compare the answer, tool permissions, and fallback behavior with the baseline before changing a default.
5. 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

OpenAI/Codex OAuth. stop rewriting the upstream authorize URL scopes so new Codex sign-ins do not fail with invalid_scope before returning an authorization code. Record the failure that this correction addresses before declaring the upgrade complete.

Audio transcription. disable pinned DNS only for OpenAI-compatible multipart requests, while still validating hostnames, so OpenAI, Groq, and Mistral transcription works again without weakening other request paths. 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.11 GitHub release. The release index gives the surrounding sequence, while the session concepts supplies the operational background.