OpenClaw v2026.4.24-beta.1: Google Meet joins OpenClaw as a bundled participant, recovery notes

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

The limits of the recovery promise

Plugin and model infrastructure is lighter at startup

static model catalogs, manifest-backed model rows, lazy provider dependencies, and external runtime-dependency repair for packaged installs.

Plugin and model infrastructure is lighter at startup changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Control UI/Talk

add browser WebRTC realtime voice sessions backed by OpenAI Realtime, with Gateway-minted ephemeral client secrets and openclaw_agent_consult handoff to the full OpenClaw agent.

Before widening access for Control UI/Talk, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Plugins/Google Meet

add a bundled participant plugin with personal Google auth, explicit meeting URL joins, Chrome and Twilio realtime transports, paired-node chrome-node support for Parallels-style Chrome/BlackHole/SoX hosts, and full-agent consults inside live voice sessions.

The useful evidence for Plugins/Google Meet is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Run the smallest useful rehearsal

1. Write down the baseline for Google Meet joins OpenClaw as a bundled participant, 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. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
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

MCP. retire one-shot embedded bundled MCP runtimes at run end, skip bundle-MCP startup when a runtime tool allowlist cannot reach bundle-MCP tools, and add mcp.sessionIdleTtlMs idle eviction for leaked session runtimes. Fixes #71106, #71110, #70389, and #70808. This is the edge case to include in a regression check, especially when the release is pre-release.

Gateway/restart continuation. durably hand restart continuations to a session-delivery queue before deleting the restart sentinel, recover queued continuation work after crashy restarts, and fall back to a session-only wake when no channel route survives reboot. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.4.24-beta.1 notes with your test result. Read the official release index for neighboring versions and the model provider reference for configuration limits.