Guide

OpenClaw v2026.5.4-beta.3: Plugins/migration, operator field notes

May 5, 20265 min readUpdated September 11, 2026By OpenClawBlog Team

The source record for v2026.5.4-beta.3 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.

Channel
Pre-Release

Primary signals
Google Meet/Voice Call; Gateway/Windows; Plugins/migration

Publication date
2026-05-05

A small field test

Google Meet/Voice Call

Evidence from the release. make Twilio dial-in joins speak through the realtime Gemini voice bridge with paced audio streaming, backpressure-aware buffering, barge-in queue clearing, and no TwiML fallback during realtime speech, giving Meet participants a much snappier OpenClaw voice agent.

Operator reading. Google Meet/Voice Call changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Gateway/Windows

Evidence from the release. bind the default loopback gateway listener only to 127.0.0.1 on Windows so libuv's dual-stack ::1 behavior cannot wedge localhost HTTP requests.

Operator reading. The best check for Gateway/Windows is deliberately narrow. Run one normal case and one boundary case, then compare the result with the previous release.

Plugins/migration

Evidence from the release. emit catalog-backed install hints when plugins.entries or plugins.allow references an official external plugin that is not installed, so upgraded configs point operators to openclaw plugins install <spec> instead of telling them to remove valid plugin config.

Operator reading. The maintainer check for Plugins/migration is a complete package review: identify the entry point, requested access, dependency tree, and uninstall behavior before publishing or upgrading.

OpenAI/Codex media

Evidence from the release. advertise Codex audio transcription in runtime and manifest metadata and route active Codex chat models to the OpenAI transcription default instead of sending chat model ids to audio transcription.

Operator reading. OpenAI/Codex media changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

The details that affect a runbook

Plugins/install

honor the beta update channel for onboarding and doctor-managed plugin installs by requesting floating npm and ClawHub specs with @beta while keeping persistent install records on the catalog default.

For Plugins/install, 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.

WhatsApp/onboarding

canonicalize setup and pairing allowlist entries to WhatsApp's digit-only phone ids while still accepting E.164, JID, and whatsapp: inputs, so personal-phone allowlists match WhatsApp Web sender ids after setup.

Read WhatsApp/onboarding as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Operator checklist before rollout

Before touching persistent state, capture the version, host, provider, and workspace for Google Meet/Voice Call.
Read the linked release record and verify a backup whenever the change can alter configuration or session data.
Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
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

Plugins/install. honor the beta update channel for onboarding and doctor-managed plugin installs by requesting floating npm and ClawHub specs with @beta while keeping persistent install records on the catalog default. Treat the fix as a boundary condition and retain the source wording beside your local result.

WhatsApp/onboarding. canonicalize setup and pairing allowlist entries to WhatsApp's digit-only phone ids while still accepting E.164, JID, and whatsapp: inputs, so personal-phone allowlists match WhatsApp Web sender ids after setup. Keep the reproduction and the post-fix result together in the acceptance record.

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