OpenClaw v2026.10.4 Patch Release Fixes Update Recovery, Chat Refresh, and Sign-In Failures

OpenClaw v2026.10.4 is out as a patch release. It targets three areas: update recovery, chats that get stuck after updates, and a batch of messaging, model-tool, and sign-in failures. The release bundles 55 PRs and 24 direct commits from 49 contributors.

Update and recovery fixes

• Removes unnecessary interruptions after system sleep or backward clock changes.
• Fixes shutdowns hanging on stalled conversation indexing.
• Eliminates false update-verification warnings.
• Stops duplicate temporary database copies during update checks.

One caveat worth reading twice: some updater improvements only apply to upgrades performed after 10.4 is installed. They do not repair an already-stuck updater by themselves. The update and recovery guide in the full notes covers the correct recovery path.

Chat refresh after updates

Chats stuck on the "Server updated" screen can now refresh back to the same conversation link. The release also reduces unnecessary dashboard reconnects when Gateways are busy.

If your chat tab was already open before updating, save unsaved work and reload it once to pick up the chat-refresh fix.

Messaging repairs

• Telegram polling failing to start.
• macOS reply failures that caused incoming messages to repeat.
• Feishu replies interrupted by settings reloads.
• Lost chunks in long IRC replies.

Discord voice changes without rejoining

You can now switch voices and keep asking for agent checks in the same call, without dropping and rejoining.

Model and agent fixes

• Reasoning with tools through the official OpenAI API.
• Claude CLI history when switching between channels and web chat.
• Launch failures affecting agent messages or subagent follow-ups.

Sign-in repairs

• MCP sign-in failures after browser consent.
• Blocking passkey prompts in headless Chromium are now dismissed, so another login method can be selected.

Passkeys themselves still require a headed browser — headless Chromium can't complete a passkey flow, only skip past the prompt.

If you're on an earlier 2026.10.x build and hit any of the above, upgrade to 10.4 and reload your open chat tabs once. If the updater is already wedged, don't count on 10.4 to unstick it — follow the recovery guide linked in the full notes.