OpenClaw 2026.5.4 Release Notes: Google Meet Voice Bridge, Windows Loopback Fix, and Codex Transcription Routing

OpenClaw v2026.5.4 was released on May 5, 2026. The official GitHub release includes one clear highlight and several platform-level changes around Windows networking, plugin migration, media routing, and workspace-aware performance.

Among the early May releases, this is the one with the most visible user-facing feature.

The Headline: Faster Google Meet Voice Joins

The official release notes say Twilio dial-in joins for Google Meet now 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.

The official Google Meet plugin documentation confirms that:

Google Meet support is provided through an explicit OpenClaw plugin.
realtime voice is the default mode.
Twilio can be used with a dial-in number plus optional PIN or DTMF sequence.

That means the May 5 release is improving an already documented Meet transport path, not introducing a speculative workflow. The release notes describe the result as a snappier voice agent experience for Meet participants.

Windows Loopback Binding Fix

OpenClaw 2026.5.4 also includes a platform-specific networking fix for Windows. The official release notes state that the default loopback Gateway listener now binds only to 127.0.0.1 on Windows so libuv dual-stack ::1 behavior cannot wedge localhost HTTP requests.

For Windows users who rely on the local Control UI or local agent access, that is the kind of infrastructure fix that can remove intermittent failures without changing everyday commands.

Plugin Migration and Codex Media Routing

The release notes also show a quality-of-life improvement for upgrades: when plugins.entries or plugins.allow references an official external plugin that is not installed, OpenClaw now emits catalog-backed install hints instead of telling operators to remove valid plugin config. That should make migration to externalized official plugins more straightforward.

On the OpenAI side, the release notes say OpenClaw now advertises Codex audio transcription in runtime and manifest metadata and routes active Codex chat models to the OpenAI transcription default instead of sending chat model IDs to audio transcription.

That change fits the broader distinction in the official OpenAI docs, where model route, auth path, and runtime are treated as separate layers inside OpenClaw.

Performance and Dependency Changes

The May 5 release also refreshed multiple runtime and provider dependencies, including Pi 0.73.0, ACPX adapters, OpenAI, Anthropic, Slack, and TypeScript native preview. At the same time, the release notes say the Bedrock runtime installer override remains pinned below the Windows ARM Node 24 npm resolver failure.

There is also an agent performance change: resolved workspace information now passes through BTW, compaction, embedded-run model generation, and PDF model setup so explicit agent-directory model refreshes can reuse the current workspace-scoped plugin metadata snapshot instead of falling back to cold scans.

That is a technical optimization, but it is directly stated in the release notes and relevant for operators who care about startup and refresh cost.

Why This Release Matters

OpenClaw 2026.5.4 stands out for two reasons:

it improves a real, documented Google Meet voice workflow
it fixes Windows localhost behavior at the Gateway level

If you use voice-enabled meeting flows, this is the most important of the May 4-7 releases. If you mainly run local Gateway setups on Windows, the loopback fix may be the more important item.

For follow-up changes that focus more on compatibility and maintenance, continue with OpenClaw 2026.5.5 and OpenClaw 2026.5.7.