OpenClaw 2026.10.7 preserves recovery provenance and unfinished tool outcomes across interrupted sessions, retires stale terminal residue before accepting a new message, and keeps rejected Claude CLI drafts out of final replies. It also makes verified updates survive later maintenance errors, resumes interrupted package updates and preserves last-known-good state through truncated writes.
Why it matters: Agent recovery can otherwise replay stale work, lose unfinished effects or treat a successful activation as failed. This release makes those failure states explicit across sessions, updates, databases, workers, backups and multi-file patches.
OpenClaw 2026.10.6 requires Node 24.22.1 or 26.12.1 and updates installers and images for October certificate-key security fixes. It also refuses unsafe updates, preserves malformed workspace and backup data, and improves queued-turn and delivery recovery across restarts.
Why it matters: The release turns a runtime security floor and data-preserving recovery behavior into an explicit production boundary. Operators on older Node builds can be blocked from upgrading until the runtime is repaired, while the migration changes affect how failure…
OpenClaw 2026.9.3 rehearses core and plugin changes in isolated candidate state, recovers abandoned update records, preserves warm caches and persistent workshop skills, and introduces several breaking runtime and SDK migrations.
Why it matters: The release strengthens upgrade recovery for a stateful agent runtime, but its new Node floor and SDK changes can block existing gateways or plugins if operators update without a compatibility checkpoint.
OpenClaw 2026.9.2 shipped at 01:30 IST with restart recovery for active, queued and delegated replies; GPT-6 Astra support; live settings updates; connected-account selection; and swarm orchestration enabled by default. It also hardens automatic updates, Git backups and corrupt-archive rejection.
Why it matters: A persistent agent runtime now preserves more work across restarts and grants multi-agent orchestration by default, changing failure recovery, model compatibility and the amount of concurrent authority operators must supervise.
OpenClaw 2026.9.1 shipped just after midnight in India with automatic rollback after failed update checks, startup recovery under load, personal skill libraries on shared gateways, durable Codex MCP approvals, routed approval cards and explicit working-directory controls.
Why it matters: Update recovery, reusable permissions, shared skills and agent worktrees all change the trust and failure boundary of a persistent agent runtime even when its model is unchanged.
OpenClaw released stable 2026.8.1 and clarified that the earlier `2026.9.1-beta.1` tag was actually 2026.8.1 beta 4. Beyond restart recovery, the stable release adds conversation search, remote workers, durable progress views, structured questions, interactive widgets, masked credential requests, scoped automation permissions, explicit model allowlists, team roles and multiple migration-sensitive default changes.
Why it matters: The corrected identity prevents a false version ordering, while the stable release changes memory, self-learning, credentials, automation, model routing and team permissions—control boundaries that can alter agent behavior without a model change.