OpenClaw 2026.10.1 is now the latest npm release. The package metadata changed at 2026-10-10 22:45 UTC, with npm reporting 2026.10.1 as latest, 2026.10.1-beta.2 as beta, and 2026.8.35 as extended-stable.
There is not a GitHub Releases page for the tag yet, but the signed Git tag v2026.10.1 exists and points at a changelog refresh commit. That makes this a package-first stable ship: the installable npm package is live, while the richer release page may still be catching up.
What Shipped
The refreshed changelog expands the audited release record from 377 to 396 unique PRs and adds several practical fix groups. The biggest themes are agent continuity, update recovery, installed-plugin startup performance, local model behavior, and channel reliability.
Highlights from the changelog include:
- Agents and subagents keep completed results through memory-saving turns, follow-up messages, reasoning-only tails, and small-context auto-compaction recovery.
- Update and Doctor paths settle prepared activations, avoid blocked rollbacks when the Gateway is stopped, and stop repeating refused update advice while recovery is still pending.
- Gateways with installed plugins avoid repeated plugin Doctor captures and regain the fast Windows startup path for large plugin installs.
- Codex, ChatGPT, Ollama, Gemma 4, and managed llama.cpp paths pick up fixes for final-token loss, rejected cached tool continuations, context errors, Tool Search, trailing tool-call text, and memory indexing.
- Telegram, Bun state ownership, Docker owner recovery, memory-wiki status, global npm installs, and local browser terminal color support all get targeted reliability fixes.
Why The npm Signal Matters
OpenClaw users often install or update through npm before reading a release page. A new latest tag means default install commands now resolve to 2026.10.1, not the earlier 2026.9.9 stable build.
That matters for operators who track stable rather than beta. The beta channel had already surfaced 2026.10.1 work earlier this week, but npm latest is the broad distribution switch. It is the version ordinary package consumers are most likely to receive.
The package metadata also includes the tarball and integrity string:
- Package:
openclaw@2026.10.1 - Tarball:
https://registry.npmjs.org/openclaw/-/openclaw-2026.10.1.tgz - Integrity:
sha512-C072/lxy83KP1nMCnJbipr4O+EtIR9XXbjzQFM+ol7VE5ci2MkKk5XTxfSG70jxpEVaGFeXcEmObHxR/ZHLdHw==
What To Watch
Because the GitHub release page is not published yet, treat npm and the signed tag as the primary public artifacts for now. The changelog commit is still useful, though: it names the added fix buckets and the PR ranges behind them.
The strongest user-facing fixes are clustered around reliability under pressure. If you run local models, large plugin installs, Windows Gateways, Docker-backed Gateways, Telegram, or frequent update/rollback flows, 2026.10.1 is the stable release to pay attention to.
Bottom Line
OpenClaw 2026.10.1 has crossed the line from beta train to npm latest. The release is broad rather than flashy: fewer headline features, more hardening across the places real Gateway operators tend to feel pain.