OpenClaw v2026.5.16-beta.3: Maintainer tooling, operator field notes

The source record for v2026.5.16-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.

A small field test

01 / Providers/xAI

Source signal. add xAI Grok OAuth login for SuperGrok subscribers, letting xai/* models and xAI media/tool providers authenticate without XAI_API_KEY.

Treat Providers/xAI as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

02 / CLI/cron

Source signal. add openclaw cron run --wait with timeout and poll interval controls, plus exact cron.runs --run-id filtering so automation can block on one queued manual run.

Keep CLI/cron inside a test workspace until you can inspect its ledger, next run, failure state, and cancellation behavior from the operator surface.

03 / Maintainer tooling

Source signal. route Crabbox skill defaults through the repo brokered AWS config, leaving Blacksmith Testbox as an explicit opt-in instead of the broad-proof default.

Keep discovery separate from permission for Maintainer tooling. Review the manifest, source, dependencies, and removal path in a disposable workspace before enabling it.

04 / Gateway/diagnostics

Source signal. redact credential-bearing gateway target URLs and client diagnostics while preserving raw connection URLs for programmatic use, so connect-failure logs no longer surface embedded tokens.

Treat Gateway/diagnostics as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

The details that affect a runbook

Telegram

normalize announce group targets via a new resolveSessionTarget channel hook so scheduled announcements resolve consistently against the same Telegram session conversation registry as inbound turns. Fixes #81229.

Telegram 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.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Providers/xAI.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

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

Gateway/diagnostics. redact credential-bearing gateway target URLs and client diagnostics while preserving raw connection URLs for programmatic use, so connect-failure logs no longer surface embedded tokens. Treat the fix as a boundary condition and retain the source wording beside your local result.

Telegram. normalize announce group targets via a new resolveSessionTarget channel hook so scheduled announcements resolve consistently against the same Telegram session conversation registry as inbound turns. Fixes #81229. Keep the reproduction and the post-fix result together in the acceptance record.

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