OpenClaw v2026.5.10-beta.4: Bonjour/Gateway, recovery notes

v2026.5.10-beta.4 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

CI

What changed. add a non-blocking plugin-inspector-advisory artifact to Plugin Prerelease so release runs capture bundled plugin compatibility triage without changing the blocking gate.

Check it with. The maintainer check for CI is a complete package review: identify the entry point, requested access, dependency tree, and uninstall behavior before publishing or upgrading.

Runtime/Fly

What changed. detect Fly Machines as container environments from their runtime env vars, so gateway bind and Bonjour defaults match remote container launches.

Check it with. A release note about Runtime/Fly becomes useful when the same task can be repeated after a restart and still produce an explainable result.

Providers/fal

What changed. route GPT Image 2 and Nano Banana 2 reference-image edit requests to /edit with image_urls array, enforce NB2 edit geometry using aspect_ratio and resolution params, lift Fal edit mode input-image caps to 10 for GPT Image 2 and 14 for Nano Banana 2, and allow aspect-ratio hints in edit mode.

Check it with. The safe reading of Providers/fal is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Bonjour/Gateway

What changed. treat active ciao probing and fresh name-conflict renames as in-progress so the mDNS watchdog waits for probe settlement before retrying, preventing rapid re-advertise loops on Windows, WSL, and other multicast-hostile hosts. Refs #74242.

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

The limits of the recovery promise

Providers/MiniMax

send a minimal Anthropic-compatible user fallback when message conversion filters a turn to an empty payload, so MiniMax M2.7 no longer returns chat content is empty after tool-heavy sessions. Fixes #74589.

The operator question around Providers/MiniMax is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Run the smallest useful rehearsal

1. Write down the baseline for CI, 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 models

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

Bonjour/Gateway. treat active ciao probing and fresh name-conflict renames as in-progress so the mDNS watchdog waits for probe settlement before retrying, preventing rapid re-advertise loops on Windows, WSL, and other multicast-hostile hosts. Refs #74242. This is the edge case to include in a regression check, especially when the release is pre-release.

Providers/MiniMax. send a minimal Anthropic-compatible user fallback when message conversion filters a turn to an empty payload, so MiniMax M2.7 no longer returns chat content is empty after tool-heavy sessions. Fixes #74589. Treat the fix as a boundary condition and retain the source wording beside your local result.

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