OpenClaw v2026.4.15-beta.2: Google/TTS, operator field notes

The source record for v2026.4.15-beta.2 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

The details that affect a runbook

Read the narrow change in context

v2026.4.15-beta.2 is a pre-release checkpoint with a deliberately small surface. The source names Anthropic/models: default Anthropic selections, opus aliases, Claude CLI defaults, and bundled image understanding to Claude Opus 4.7. A narrow patch still has a clear job: it should remove one failure or preserve one compatibility promise without changing unrelated configuration.

Keep this patch beside the operator's maintenance notes. Compare the installed tag, package version, and service owner before applying it. If this entry is a correction release, record the broken behavior that led you here, then repeat that exact scenario after the update. That evidence is more useful than a general claim that the package installed successfully.

The adjacent source detail is Google/TTS: add Gemini text-to-speech support to the bundled google plugin, including provider registration, voice selection, WAV reply output, PCM telephony output, and setup/docs guidance. Read both signals together, because a hotfix can alter the boundary around a plugin, channel, session, or installer even when the version number looks like a minor suffix.

A small worksheet for this version

• Write the old version, the new version, and the package or tag that actually changed.
• Capture one reproduction before the update and the same reproduction after it.
• Record the first useful log line, the final user-visible result, and any rollback command that was tested.
• Leave unrelated channels, skills, and provider defaults untouched until the correction is understood.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Anthropic/models.
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 models

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

Gateway/tools. anchor trusted local MEDIA: tool-result passthrough on the exact raw name of this run's registered built-in tools, and reject client tool definitions whose names normali. Treat the fix as a boundary condition and retain the source wording beside your local result.

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