OpenClaw May 2026: Mobile, Plugins, and Recovery

OpenClaw's May work is easy to miss because it is spread across many small fixes. v2026.5.28, published on May 30, gives the month a useful shape: recover cleanly, keep channel identity intact, and make mobile and plugin behavior easier to inspect.

Recovery keeps its context

Subagents now keep their working directory and workspace separation more reliably. Session locks release after a timeout without deleting a live OpenClaw lock, and stale restart continuations are avoided. These are unglamorous changes, but they determine whether a failed run can be retried without corrupting the next one.

The same release improves diagnostics for CLI, authentication, Doctor, and provider setup. When a model or service cannot start, the error is more likely to tell you which layer needs attention.

Channels preserve identity

May fixes cover WhatsApp, Matrix, iMessage, Slack, Discord, Telegram, and Microsoft Teams. The common thread is message identity: a reply should return to the conversation that requested it, and a reconnect should not quietly duplicate or lose the result.

Test this with a harmless message after an upgrade. Send one request, interrupt the connection, reconnect, and confirm that the final reply appears once in the intended thread.

Mobile and plugin surfaces move forward

The iOS Pro UI, hosted push relay defaults, Talk playback, Gateway chat transport, onboarding, and WebChat reconnect behavior all receive updates. ClawHub gains plugin display names plus verification and trust surfaces. The release also adds official provider catalogs and a GitHub Copilot agent runtime path.

openclaw --version
openclaw doctor

Do not treat a verified label as a substitute for reviewing permissions. The official security guide still recommends a clear trust boundary and separate installations for people who do not trust one another.

A measured May upgrade

1. Back up configuration and session data.
2. Upgrade and run Doctor before reconnecting channels.
3. Check one direct message and one media reply.
4. Review plugin trust and provider credentials.

For exact fixes and later patches, keep the release index beside your runbook.