OpenClaw releases 2026.5.19 with realtime Android Talk Mode and headless xAI login

• openclaw's 2026.5.19 release thread says OpenClaw moved Android Talk Mode onto realtime Gateway relay voice sessions, with streaming mic input, realtime audio playback, tool-result bridging, and on-screen transcripts.
• According to openclaw's xAI login update, xAI setup now supports device-code OAuth, which removes the localhost browser callback requirement on headless or remote machines.
• openclaw's Telegram update and the prior 2026.5.18 Telegram reliability pass both frame the Telegram work as thread-safety plumbing, not a flashy feature, with forum-topic delivery, DM draft previews, and safer reconnect behavior getting tightened.
• openclaw's browser-dialog post adds a small but useful browser-agent fix: runs can now surface pending dialogs, report blockedByDialog, and target the right prompt by ID instead of silently stalling.

The official 2026.5.19 release page is short, but the linked docs are where the practical changes live: Android platform docs, xAI provider docs, Telegram channel docs, and browser tool docs. The quiet reveal is that OpenClaw spent two consecutive releases removing the annoying failure modes around remote use, voice streaming, auth on headless boxes, and browser modals.

OpenClaw's Android client now routes Talk Mode through realtime Gateway relay voice sessions. As openclaw's Android post describes it, that stack includes streaming microphone input, realtime audio playback, tool-result bridging, and transcripts shown in the app.

The same feature appeared one day earlier in openclaw's 2026.5.18 Android note, which suggests 2026.5.19 is the stabilization pass, not the first appearance. The relevant reference point is the Android docs.

The most concrete remote-ops improvement is xAI login on machines without a local browser. openclaw's xAI login update says setup now uses device-code OAuth, so authorization can happen without a localhost callback.

That closes out the auth cleanup started in openclaw's 2026.5.18 release thread and openclaw's earlier xAI note, which mentioned sidecar auth fixes, token exchange fixes, and fewer broken auth profiles. OpenClaw also paired that work with a broader Grok integration push in openclaw's Grok integration announcement and testingcatalog's summary, backed by xAI's own integration post.

OpenClaw keeps spending release budget on Telegram thread integrity. openclaw's 2026.5.18 Telegram note said generated media completions now stay in forum topics, replies preserve thread IDs, and topic sends fail closed instead of leaking into the base chat.

The 2026.5.19 pass adds three more concrete pieces, per openclaw's Telegram update:

• steadier forum-topic handling
• native DM draft previews for transient progress
• safer delivery around reconnects, verbose progress, and generated media

The implementation surface is documented in the Telegram channel docs.

Browser runs now expose modal state instead of getting mysteriously stuck. According to openclaw's browser-dialog post, snapshots can show pending and recent dialogs, actions can return blockedByDialog, and the browser dialog flow can answer the correct prompt by ID.

That builds directly on openclaw's 2026.5.18 browser note, which described the same modal-awareness work one release earlier. The behavior is surfaced in the browser docs, and it is the clearest example in this release of OpenClaw turning an agent dead-end into a debuggable state.