A patched Node is required
OpenClaw v2026.10.6 requires a patched Node and stops losing replies across restarts
OpenClaw now requires a patched Node 24 or Node 26. Those October Node.js security releases reject TLS chains signed with compromised certificate keys. Everything else in this release is a reliability fix.
Update refuses an old Node
OpenClaw v2026.10.6openclaw update stops on an unpatched Node
On an older Node, the OpenClaw update command now refuses before it installs anything and explains how to recover, so your running install keeps working. Docker images and installers already ship the patched runtimes.
Updates recover
OpenClaw v2026.10.6Updates recover on Windows and macOS
Updates through Windows and macOS package managers now recover from platform-specific failures. A package swap refuses to run while the service is in an unsafe state, and a frozen Gateway startup can be retired cleanly.
Migrations keep your data
OpenClaw v2026.10.6Migrations and backups keep your data
OpenClaw Doctor and migrations now refuse a workspace import that is malformed or would lose data. Malformed Notes bytes are preserved, deeply nested SQLite backups are kept, and a failed restore check keeps its staging files.
02: Replies and restarts
OpenClaw v2026.10.6What happens to your messages when the Gateway restarts.
Replies survive a restart
OpenClaw v2026.10.6Replies survive a restart and arrive once
Queued turns, watched child results, dead-lettered deliveries and streamed replies now survive a Gateway recovery. They no longer vanish or arrive twice, and the missing-answer notice appears only when an answer is missing.
Channels keep every message
OpenClaw v2026.10.6WhatsApp, Telegram, Slack and Discord keep every message
Four chat channels stop losing or duplicating messages. The fixes cover WhatsApp retries and stickers, Telegram albums and dual-stack replies, Slack relay recovery, and replies during Discord voice calls.
Workers come back
OpenClaw v2026.10.6Workers and worktrees come back after a reboot
After a reboot, OpenClaw worker hosts now reclaim their capacity. Worktrees made from a partial git clone repair their missing objects, and child results and exec wake-ups survive a Gateway restart.
03: Agents and models
OpenClaw v2026.10.6How agents, tools and models handle failure.
Providers behave the same
OpenClaw v2026.10.6Tool calls behave the same on every provider
Tool calls now behave consistently across providers, including GPT-5.6 tool turns and DeepSeek tool calls through OpenRouter. LM Studio recovers from context overflow, and model retry and fallback budgets work the same everywhere.
Stuck tools time out
OpenClaw v2026.10.6A stuck tool call times out where you can see it
An unfinished tool call now times out visibly. Large patch hunks stop crashing on argument limits, context overflow compacts after steered tool results, and a yielded task you stop stays stopped.
Scheduled follow-ups
OpenClaw v2026.10.6Scheduled follow-ups keep your authority
next_check to check back laterA follow-up scheduled from an authorized operator's turn now runs with that operator's current authority. And a one-shot continuation can call the next_check tool to check back later.
Codex sessions
OpenClaw v2026.10.6Codex sessions outlast a runtime restart
Codex and native sessions now keep their conversations across a runtime restart. Workspace bindings survive a reply reset, and a stalled startup or a finished subagent is released after a cancellation or a failed cleanup.
04: Platforms
OpenClaw v2026.10.6Windows, iOS, and who has to wait.
Windows and iOS
OpenClaw v2026.10.6Windows starts and iOS reconnects
On Windows, a fresh state store, a Proxy-backed environment or a stored Anthropic credential no longer stops OpenClaw from starting. On iOS, Talk and chat recover from first-reply and timeout failures.
Android waits
OpenClaw v2026.10.6Android waits for a later release
No new Android APK this release. The app stays on its August build.
Android users have to wait. This release ships without a new Android APK, so the OpenClaw Android app stays on its August build.
Which Node?
OpenClaw v2026.10.6Which Node does your OpenClaw Gateway run on?
The supported Node versions and the upgrade steps are in OpenClaw's Node.js guide and Updating guide. Which Node version does your OpenClaw Gateway run on today?
