OpenClaw v2026.5.10-beta.5: MiniMax, provider notes

v2026.5.10-beta.5 changes how an agent selects, calls, or remembers a provider. The official record describes a provider, model, voice, or context change; the useful test is a small request with the provider boundary recorded.

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

Provider and model consequences

01 / CI

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

Use CI to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

02 / Runtime/Fly

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

The best check for Runtime/Fly is deliberately narrow. Run one normal case and one boundary case, then compare the result with the previous release.

03 / Providers/fal

Source signal. 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.

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.

04 / Bonjour/Gateway

Source signal. 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.

Use Bonjour/Gateway for a small reproducible task: save the input, visible result, useful failure, and version context another operator would need.

What changes outside the chat box

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.

Providers/MiniMax lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to CI.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw models

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

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. Record the failure that this correction addresses before declaring the upgrade complete.

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. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.5.10-beta.5 GitHub release. The release index gives the surrounding sequence, while the model provider reference supplies the operational background.