OpenClaw shipped v2026.9.4 on September 11th at 03:46 UTC, bringing a broad stable update for operators who care about recovery, plugin management, prepared cloud sessions, and day-to-day chat reliability.
This is a dense release. The headline is not one single feature; it is a stronger operating surface around updates, plugins, cloud workers, terminal prompts, image generation choices, voice delegation, and externally managed configuration.
The release notes describe several changes that matter most in production: compatible failed updates can roll back to the retained previous package, the Plugins workspace now centralizes bundled and ClawHub discovery, and eligible Linux cloud sessions can start from prepared local projects or public GitHub repositories.
What Changed
The update recovery story is the most operationally important part of OpenClaw 2026.9.4. The release says compatible schema-neutral update failures can restore the previous package, command shim, service, and pre-activation configuration, then verify the prior Gateway again. Database migrations still require a verified backup, and incompatible schema or configuration changes block automatic rollback.
That is the right boundary. Automatic rollback is useful only when the system can prove it is returning to a known shape. OpenClaw is drawing that line around package state, service ownership, configuration, and database compatibility instead of treating every failed update as reversible.
Plugin management also gets a major usability lift. The release brings installed plugins, bundled plugins, and ClawHub discovery into a single Plugins workspace. It adds category browsing, tighter detail pages, short plugin-page URLs, and unified search across installed and ClawHub skills.
For cloud users, prepared sessions move closer to a warm-start model. Eligible local Git projects and public GitHub repository sessions can reuse prepared workers and build reusable snapshots from Control UI before a conversation starts. OpenClaw notes that private repository-only sessions and paired devices remain outside this flow, and that ready workers can create provider running-machine charges until deleted.
Developer And Operator Notes
Terminal users get a more capable question flow. OpenClaw can now handle keyboard-driven choices, free-text answers, multi-select prompts, and multi-question prompts in Gateway-connected and local TUI sessions. A pending prompt can be reopened with /question.
Model and media workflows also move forward. The release adds selectable GPT Image 2.5 Flare and Sunburst variants through OpenAI or fal, while preserving existing default model choices. Deepgram voice notes can use Flux models when ffmpeg is available.
OpenClaw also adds OPENCLAW_CONFIG_READONLY=1 for deployments where configuration is managed outside the app. In that mode, OpenClaw avoids rewriting deployment-managed configuration while still allowing diagnostics and ordinary runtime state.
Reliability Themes
The release spends a lot of space on fixes around reply delivery, history handoff, channel behavior, provider selection, memory, update restart, plugin installation, and Gateway responsiveness. The common thread is preserving the right state when a long-running system crosses a boundary: network failure, reload, provider fallback, channel delivery, update handoff, archive cleanup, or restart.
Among the notable fixes:
- Final replies recover after interrupted streams and earlier tool errors.
- Timeout notices and partial failed-turn text are retained after reload.
- Provider and model selections preserve exact identity and supported controls.
- Cloud metadata addresses remain blocked when private IPv6 exceptions are enabled.
- Workspace edits, backups, migrations, and update captures keep tighter safety boundaries.
The release verification is candid about what passed and what remains pending. Stable validation, core npm publication, Docker publication, macOS artifacts, and the stable update feed are reported as verified. ClawHub recovery, beta-selector synchronization, and some native distribution follow-ups remain pending.
Why It Matters
OpenClaw 2026.9.4 reads like a release for real installations rather than demos. Safer update recovery, clearer plugin management, prepared cloud sessions, better terminal prompts, and stronger history recovery all reduce the friction around running agents for longer periods.
The practical takeaway is simple: if you run OpenClaw as infrastructure, this release is worth testing. The new features improve the control plane, while the fixes keep conversations, credentials, plugins, updates, and channel delivery from drifting into ambiguous states when something goes wrong.