OpenClaw v2026.4.11-beta.1: Dreaming/memory-wiki, recovery notes

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

Failure and recovery path

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. A successful click does not establish Dreaming/memory-wiki. Compare the state before and after a reload, then verify that a user can tell what happened without reading internal logs.

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. For Tools/video_generate, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

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. Treat OpenAI/Codex OAuth as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

The limits of the recovery promise

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.

Run the smallest useful rehearsal

1. Write down the baseline for Dreaming/memory-wiki, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Use a disposable session to compare the new model or provider with the previous route on one fixed input.
4. Restore the previous provider setting after the check and retain the measured result beside the release tag.
5. 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

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. This is the edge case to include in a regression check, especially when the release is pre-release.

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. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.4.11-beta.1 notes with your test result. Read the official release index for neighboring versions and the session concepts for configuration limits.