OpenClaw · 2026-09-11 · major
OpenClaw 2026.9.4 — plugins and skills install from the Control UI
OpenClaw 2026.9.4 moves plugin and skill management into the Control UI, so bundled and ClawHub plugins install without the CLI. The release lands 1,558 pull requests from 293 contributors and can roll back a failed update.
OpenClaw 2026.9.4 gives plugins and skills one workspace in the Control UI, and lets a failed update roll itself back.
Key specs
| Pull requests merged | 1,558 |
|---|---|
| Contributors | 293 |
Quick facts
| Version | v2026.9.4 |
|---|---|
| Maker | OpenClaw (open-source project) |
| Language | TypeScript |
| What's new | Plugin and skill discovery inside the Control UI |
| Image generation | GPT Image 2.5, Flare and Sunburst variants |
| Upgrade note | OPENCLAW_CLAUDE_CLI_LOG_OUTPUT removed — use OPENCLAW_CLI_BACKEND_LOG_OUTPUT |
| GitHub stars | 389,509 |
What is it?
Plugin and skill management moves into the Control UI in OpenClaw 2026.9.4. A single workspace now finds bundled plugins and ClawHub plugins, installs them, and sets who may use them, and it makes visible which skills the agent picked up from past conversations. OpenClaw is an open-source agent runtime that connects a model to your machine, your terminal and your apps.
How does it work?
Plugin names resolve in a fixed order: bundled plugins first, then the official external catalogs, then npm. ClawHub is the search surface for community plugins and supplies version metadata, scan results and install hints, while npm, Git refs and local paths stay available as installation sources. Deny lists beat allow lists, and workspace-origin plugins stay off by default.
Why does it matter?
Failed updates stop being a manual repair job. When an update breaks and schema checks say it is safe, 2026.9.4 restores the previous packages together with their configuration. Cloud work gets steadier too: eligible Linux sessions can start from a prepared local project or a public GitHub repository, and snapshots are reusable across conversations.
Who is it for?
self-hosters and teams running OpenClaw gateways
Frequently asked questions
- Do I need to change anything before upgrading to OpenClaw 2026.9.4?
- OpenClaw 2026.9.4 removes the OPENCLAW_CLAUDE_CLI_LOG_OUTPUT alias, so switch to OPENCLAW_CLI_BACKEND_LOG_OUTPUT first. Mac users on Bun should run brew install sqlite to keep memory search working, and anyone using a custom SQLite startup script must replace it with the OPENCLAW_SQLITE_LIBRARY setting or the gateway will fail to start.
- What happens if an OpenClaw update fails partway through?
- Recovery is built into OpenClaw 2026.9.4. For compatible failed updates, the installer restores the previous packages along with their configuration, but only after schema checks confirm the rollback is safe. Large installations should still allow extra time for the repair step, which the release notes call out explicitly as part of the upgrade procedure.
- Where can OpenClaw plugins be installed from?
- OpenClaw supports four installation sources: ClawHub for native discovery with version metadata and scan results, npm for direct registry workflows, Git for a branch, tag or commit, and local paths for development. A bare package name resolves to a bundled plugin first, then the official external catalogs, then npm as the fallback.
- Does 2026.9.4 change which models OpenClaw uses by default?
- No. OpenClaw 2026.9.4 adds support for OpenAI's GPT Image 2.5, including the Flare and Sunburst variants, for both image generation and image editing, and the release notes state that default models are unchanged. Codex subagents also gain native transcripts, so their work is readable without a separate export step.
Try it
openclaw plugins search "calendar"