OpenClaw published two release signals after this morning's aggregation window: the stable OpenClaw v2026.10.3 release and the follow-up v2026.10.5-beta.3 release. npm also moved latest to 2026.10.3, while the beta dist-tag advanced to 2026.10.5-beta.3.
The stable release is the more important production story. Its changelog says OpenClaw 2026.10.3 fixes update blockers, preserves saved sign-ins and memory files during affected Doctor repairs, helps the Mac app connect during local setup, and lets conversations continue after compaction or interrupted provider replies.
That is not a flashy feature release. It is the kind of maintenance-heavy release that matters when OpenClaw is running as infrastructure.
What Stable Users Get
The v2026.10.3 changelog groups much of the work around update and maintenance recovery. Several fixes address cases where leftover recovery records, interrupted 2026.9.8 updates, abandoned npm updater copies, Windows path differences, pnpm service commands, and briefly busy state databases could block or confuse the next upgrade.
For operators, the pattern is clear:
- Updates get better at clearing eligible stale state.
- Doctor reports more useful next steps when maintenance is unfinished.
- Recovery copies include more of the data that matters before repair.
- Update checks are less likely to mistake their own bookkeeping for user-caused change.
The release also calls out a privacy and continuity fix: Doctor no longer discards saved OAuth profiles when an unreadable legacy auth file blocks cleanup. That is an important quality bar for repair tooling. A recovery command should avoid making credential loss worse while it is trying to help.
Mac, Models, and Messaging
The stable release is not only about updates. The Mac app gets fixes for eligible "On this Mac" setups that previously failed with "Gateway rejected auth", plus reconnection after trusted Gateway certificate renewal. On the provider side, Meta users get Muse Wonder support, MiniMax gets M3.1 Flash Preview support, and interrupted ChatGPT replies can continue from saved conversation state within existing retry limits.
Messaging also receives practical reliability fixes. Channel tools keep working after the task that started or restarted a messaging account finishes, and recovery scanning avoids stealing a message that already has an active sender.
Those are small details, but they are exactly the details that make chat-driven systems feel dependable.
What Beta 3 Adds
The beta release continues the same reliability arc, but with a broader preview surface. Its highlights include update paths that leave the Gateway running, recovery for stuck package activation journals, Doctor fixes that keep credentials and data, restart survival for interrupted turns and subagent work, and Telegram spool handling that prevents old updates from replaying as new instructions.
The beta also adds Meta Muse Wonder with tools, image input, streaming, reasoning controls, and a 1M-token context window, and restores a deprecated createSessionHeaderLink export for plugins built against OpenClaw 2026.10.1 and 2026.10.2.
Why This Release Matters
OpenClaw's release stream has been heavy on update, Doctor, Gateway, and session durability work all week. v2026.10.3 is the stable consolidation point for a lot of that effort.
If you run OpenClaw casually, the headline is simple: fewer stuck updates and more resilient setup paths. If you run it as a long-lived agent host, the bigger story is stronger repair behavior around credentials, memory, plugin state, Mac app trust, and interrupted model replies.
The beta channel then previews the next layer: keeping Gateway services alive through more update shapes, protecting Telegram users from stale legacy spool replay, and extending restart recovery deeper into turns, automations, nodes, and subagents.
Bottom Line
OpenClaw 2026.10.3 is a maintenance release with real operational weight. It moves stable users forward on update recovery, Doctor safety, Mac setup, provider continuity, and messaging reliability.
The beta 2026.10.5-beta.3 release shows where the next stable track is heading: more update paths that recover cleanly, fewer restart edge cases, and a wider model/provider surface without sacrificing the repair work that keeps running systems boring.