OpenClaw v2026.9.3 Released — Enhancing Update Process Security and Implementing Breaking Changes in SDK

By the editors ／ Model: gemma-4-26b-a4b-it-qat-6bitAs of: 2026-09-08 / Updated: 2026-09-25

This article is a translation. Read the Japanese original

OpenClaw has released v2026.9.3, aimed at enhancing the security of the update process and optimizing performance.

Enhanced Update Process Security: A new feature has been added to rehearse core and plugin changes in an isolated candidate state before activation. Additionally, a recovery function for interrupted update logs has been implemented.
Performance Optimization: Includes retention of warm prompt caches, reduction of unnecessary processing during cold session updates, and reuse of worker builds across sessions.
Skill Workshop Improvements: Agents can now maintain skills as a single persistent collection, and a full comparison feature for skill instructions has been added.
UI/UX Enhancements: Introduced monitoring of browser tab repaints, native tab support for external links on macOS, and selective activation of team activity reports.
Strengthened Management Functions: Users can now directly manage connected accounts and set priority for supported accounts from the Models settings.

Stabilized Updates and Recovery: Improvements have been made to rollback procedures upon update failure, avoidance of mismatches during updates, and measures to prevent service disruptions caused by improper updates.
Improved Session and Connection Reliability: Improvements to active session visibility, state retention during connection loss, and fixes for authentication errors when connecting to various providers.
UI Bug Fixes: Fixed diagnostic information display on Android, maintenance of message formatting in Discord and Telegram, and various dashboard display issues.

Node.js Requirement Changes: Node 24.16.0 or later, or Node 26.1.0 or later is now required. Node 22, Node 25, and previous 24.x/26.x builds are no longer supported.
SDK Specification Changes: Helper functions have been moved within the execution-policy SDK and approval SDK, and changes have been made to method names and type definitions. Additionally, the return value format of MCP prompt adapters has been changed to be a typed MCP GetPromptResult.

Sources