OpenClaw 2026.10.4 Stabilizes Gateway Sleep Recovery and Closes Tlon Owner Impersonation as 10.10 Beta Lands
Stable 2026.10.4 landed overnight as a no-new-features patch for 10.3, keeping Gateways alive after sleep and clock jumps and closing the Tlon group-DM owner-impersonation path that yesterday's beta still carried alone. Parallel to that, 2026.10.10-beta.1 opens a larger cycle with faster Gateway internals, restart-safe replies, and ClawHub packages exposed to the Gateway.
Stable 2026.10.4 Patches Gateway Sleep, Shutdown, and Tlon Authority
The OpenClaw v2026.10.4 stable release notes on GitHub published at 5:36 PM Pacific on October 15 (2026-10-16T00:36:19Z). The tag is not a prerelease. The Changes section calls it a stability patch for 2026.10.3 with no new features or configuration changes. The OpenClaw docs page for the 2026.10.4 release frames the same build around update and recovery repairs, chats stuck after an update, and messaging, model-tool, and sign-in fixes, counting 55 pull requests, 24 direct commits, and 49 contributors. The official @openclaw post announcing the 2026.10.4 patch later that evening thanked those contributors and pointed operators at the docs page.
GitHub highlights lead with fleet-visible stability. The Gateway keeps running after the computer sleeps or the system clock jumps, instead of restarting itself because its ownership heartbeat looked stale (#170790). Shutdown and restart no longer hang on a stalled transcript worker or in-flight session lifecycle events (#170493, #170555). Headless browser pages keep responding to clicks while a site waits for a passkey (#170857). Manual /compact settles the active run before compacting instead of aborting it and dropping the pending request (#166163).
The security highlight operators should not miss: Tlon group DMs no longer treat other participants as the owner, closing an owner-impersonation path (#165801). Yesterday's coverage correctly noted that this fix appeared in 2026.10.5-beta.4 and was absent from stable 10.3. It is now listed in the stable 10.4 highlights. The docs page adds that a group DM claiming to be from the owner could previously let an allowed sender chat while replies went to the impersonated sender's private conversation, and after approving a pending DM saved before updating, the sender should be asked to resend it.
Further down, 10.4 continues update and Doctor hardening: Gateway stays responsive during long reply-tagged streams (#166782, #171573); updates stop repeating settled plugin upgrades as pending and give snapshot failures accurate recovery advice; Doctor no longer refuses unreferenced retired OAuth sidecars. Messaging repairs cover Telegram polling workers, Discord agent consults after voice changes, Feishu config hot-reload, and IRC long non-ASCII replies. The audited contribution record covers 61 unique pull requests in the v2026.10.3..d58dd3ce range.
Treat 10.4 as the production landing for anyone still on 10.3 who paused for sleep-wake restarts, hung shutdowns, or Tlon group-DM risk. It is the first stable tag that lists #165801, so Tlon fleets should not wait for the next feature train. Preview with openclaw update --dry-run, then take a single host through sleep, a forced restart, and a 1:1 Tlon owner command before widening the rollout.
2026.10.10-beta.1 Opens a Larger Feature Cycle
The OpenClaw v2026.10.10-beta.1 prerelease notes on GitHub published earlier on October 15 at 11:03 AM Pacific (2026-10-15T18:03:07Z). Where 10.4 adds no features, beta.1 starts a new line. Highlights lead with a faster Gateway: chat turns, session lists, startup, and idle Gateways do far less SQLite and main-thread work, with more database work on worker threads. Updates that finish and recover cover upgrades from 2026.10.1 and earlier betas. Restart-safe replies resume interrupted work after a Gateway restart instead of disappearing.
Cloud sessions move between local and cloud from the session menu, with environment recipes and verified Node toolchains. The Windows desktop app and fresh Tauri installs can run a local Gateway; fresh macOS installs start in guided dashboard setup. New models arrive as Gemini 4 Argon becomes the default Gemini model alongside Gemini 3.8 Flash, Nemotron 3.5 Super VL and xAI Imagine Image 2.0 land, and Meta models run through Muse Code. OpenClaw now requires macOS 26.2, iOS 26.2, and Safari 26.2 or newer (#168595). Experimental PostgreSQL for the Workboard store is also in this beta. ClawHub packages are exposed to the Gateway with portable manifest categories (#171622, #171532).
Watch note: the nested-effect Doctor work tracked as GitHub issue #168750 about nested-effect Doctor failures and pull request #170070 that landed the nested-effect Doctor fix on main is not called out in the stable 10.4 highlights, and a careful pass of the 10.10-beta.1 notes does not clearly list those identifiers either. Operators who hit nested Doctor failures should keep watching for a stable tag that names the fix and keep openclaw update repair in the runbook.
Stage 10.10-beta.1 only on disposable Gateways if you need the ClawHub-to-Gateway path, cloud session recipes, or the new model defaults. The Apple 26.2 floor will block older Mac and iOS nodes before any feature benefit shows up, so inventory device OS versions first. For production, prefer 10.4 today and treat beta.1 as a preview of the next stable train.
Security Practice: Tlon Owner Commands Belong in a 1:1 DM — Now on Stable
Stable 10.4 closes Tlon group-DM owner impersonation (#165801)
Yesterday's beta.4 notes were the first place many fleets saw #165801. Today that same fix is in stable 10.4. The OpenClaw Tlon channel documentation on owner authority and group DMs explains the rule: Tlon does not verify who wrote a group DM message, so group DM messages never carry owner authority. Owner commands, approval replies, and admin commands work only in a 1:1 DM with the bot. A group DM whose claimed author is on dmAllowlist is still answered, but as an ordinary unverified sender. Pending DM requests saved by older versions cannot be told apart from group DM claims; approving one still adds the ship to the allowlist, but its stored message is not replayed.
- Set
channels.tlon.ownerShipto your own ship so unauthorized requests queue for approval instead of being silently dropped. - Keep
dmAllowlistshort; an empty list admits no DMs except from the owner. Leave group authorization at itsrestricteddefault. - Issue approvals and admin commands only in a 1:1 DM, and treat anything in a group DM as unverified input.
- After upgrading to 10.4, re-check Tlon owner commands from a 1:1 DM and ask any sender whose pre-upgrade pending DM you approved to resend it.
Authority should come from a verified identity path, never from a display name inside a shared conversation. Stable 10.4 finally makes that rule enforceable for Tlon fleets that refuse betas.
Ecosystem Tool: ClawHub Packages Reach the Gateway in 10.10-beta.1
ClawHub registry packages exposed to the Gateway (#171622, #171532)
Beta.1 states that ClawHub exposes published packages to the Gateway and accepts portable manifest categories (#171622, #171532). The OpenClaw ClawHub documentation for searching and installing skills and plugins describes ClawHub as the public registry for OpenClaw skills and plugins. Native openclaw commands search, install, and update skills and install plugins from ClawHub; a separate clawhub CLI covers registry auth and publishing. Skills are versioned text bundles with SKILL.md; code plugins carry compatibility metadata. Plugin installs validate advertised pluginApi and minGatewayVersion before archive install, and when a package publishes a ClawPack artifact, OpenClaw prefers the exact uploaded npm-pack .tgz and verifies the ClawHub digest header.
The OpenClaw skills documentation on SKILL.md loading and discovery reminds operators that skills are markdown instruction files loaded from workspace, project, personal, managed, workshop, and bundled roots with clear precedence. Pair that with ClawHub's install flow: openclaw skills search, openclaw skills install, and openclaw plugins install clawhub:<package>. Review the listing, compatibility metadata, and security scan summary before enabling anything on a production Gateway, and prefer a disposable profile when trying a new package from 10.10-beta.1. Do not assume stable 10.4 already exposes ClawHub packages the same way.
Android Update Live, Open Together Tonight in San Francisco
Maintainer Hannes Rudolph reported that the Android app cleared Google Play review in under 24 hours and that the new update is live; the @hrudolph post on the Android Play review turnaround was amplified by an @openclaw retweet. The OpenClaw Android platform documentation for the companion node app frames the app as a companion node that requires a running Gateway on macOS, Linux, or Windows via WSL2. No Play Store version number is stated in the announcement, so treat the post as an availability signal rather than a version claim.
Calendar note for today: Open Together with Hugging Face is the free kickoff for Open Source AI Week. The Open Together event page on Luma for Friday October 16 in San Francisco lists a meetup and community demos from 6 to 9 PM at The Midway, then a dance party until midnight. The official @openclaw reminder for Open Together with Hugging Face still stands for Friday's gathering.
Use the Android refresh as a pairing-and-permissions check, not a reason to chase an unverified Play version string. Confirm the phone still points at the intended Gateway after the update, and keep owner commands off shared channels the same way Tlon now enforces on stable 10.4. If you are in San Francisco tonight, the Open Together demos are a useful place to see how other builders package skills before wiring ClawHub packages into a beta Gateway.
Need help rolling 10.4 and staging 10.10 safely?
SEN-X helps teams plan stable patch rollouts, Tlon owner boundaries, ClawHub package review, and disposable beta Gateways.
Contact SEN-X →