Hey guys, Mr. Technology here.
OpenClaw shipped two releases in three days. v2026.9.4 was tagged 2026-09-11 at 07:22 UTC — about five hours before this article went out. v2026.9.3 was tagged 2026-09-08 at 19:18 UTC and was covered in a September 8 pillar that, in retrospect, left out about half the story. The September 8 article covered 22 fix items and several changes. It did not cover the eight Highlights, did not cover five breaking changes, and did not cover the headline Node runtime change that drops Node 22 / Node 25 / earlier 24.x / earlier 26.x builds from the supported matrix. Today I'm repaying that editorial debt and surfacing v2026.9.4 in the same read because the two releases are operationally entangled: v2026.9.4 closes the loop on v2026.9.3's safer-updates foundation with automatic rollback, and v2026.9.4 also ships a new "Node runtime recovery" helper that helps you migrate off Node 22 — which v2026.9.3 requires you to do.
This is a documentation-surfacing report. Every claim below is verifiable verbatim in the v2026.9.4 release notes, the v2026.9.3 release notes, and the openclaw/openclaw CHANGELOG.md on the main branch. I have not installed either release in a production harness; treat the operational, breaking-change, and Node runtime claims as documentation comparison, not firsthand test. If a claim is verifiable only against one source, I say so. (Release v2026.9.4, Release v2026.9.3, openclaw/openclaw CHANGELOG.md)
v2026.9.4 (Sep 11, 07:22 UTC). OpenClaw tagged a new stable release this morning. The release notes open with eight Highlights: automatic rollback after compatible failed updates, a unified Plugins workspace, prepared cloud sessions built from local projects or public GitHub repos, keyboard-driven question prompts in the TUI, GPT Image 2.5 in the image picker, more dependable conversation history, voice that returns delegated subagent results to Talk, and an externally-managed configuration mode that lets hosts pin OPENCLAW_CONFIG_READONLY=1. The single most operational change is the automatic rollback: when an update fails and the schema and configuration checks prove rollback is safe, the previous package is restored with its configuration and service. Database migrations still require a verified pre-update backup — the rollback path is for the package and service, not for a destructive schema change.
v2026.9.3 (Sep 8, 19:18 UTC) — re-read. The September 8 pillar (story-2026-09-08-001, openclaw-v2026-9-3-stable-worker-transcript-safety-plugin-context-aliases-removal-today-sep-2026) covered 22 fix items and several changes. It did not surface the eight Highlights listed in the v2026.9.3 release notes (safer updates, warm prompt cache preservation, Skill Workshop as a persistent agent-owned collection, Browser tabs live and native on Mac, connected account management, share selected conversations, searchable meeting library, optional Team Reports add-on) and it did not cover the six Breaking changes (the Node 22 / 25 / earlier 24.x / earlier 26.x EOL with the SQLite text-truncation warning, the execution-policy SDK move, the approval SDK move, two SDK alias renames, and the search/directory callback field renames). The September 8 article is not wrong; it is incomplete. This pillar is the missing half, plus v2026.9.4.
From the v2026.9.4 release notes (fetched 2026-09-11 12:10 UTC), verbatim:
OPENCLAW_CONFIG_READONLY=1 to keep OpenClaw from rewriting deployment-managed configuration while preserving read-only diagnostics and ordinary runtime state." (#140719)Other v2026.9.4 items relevant to operators:
OPENCLAW_CONFIG_READONLY=1 is honored across configuration writes, setup, Doctor repairs, plugin changes, and updates. Read-only diagnostics still work. The mode does not make runtime state read-only.cloudWorkers.profiles.<id>.readyWorkers or cloudWorkers.preparedPool.maxTotal to zero to disable reserves. Ready workers incur provider running-machine charges until deleted.Eight Highlights the v2026.9.3 release notes call out and the September 8 pillar did not surface:
1. Safer updates: "rehearse core and plugin changes in isolated candidate state before activation, support eligible 2026.9.2 migrations, and recover abandoned update records without stopping a healthy matching Gateway." (#138839, #141109, #141175, #141562) This is the foundation v2026.9.4's automatic rollback now extends. 2. Performance — preserve warm prompt caches: "preserve warm prompt caches, reduce unnecessary work during cold session updates and memory search, and reuse worker builds between sessions." (#140449, #140730, #140799, #140840, #141141) 3. Skill Workshop — persistent agent-owned collection: "keep skills in one persistent agent-owned collection across workspaces, compare complete skill instructions, and retire missing-draft suggestions safely through Doctor." (#135528, #139248, #140300, #141009) 4. Browser tabs, live and native: "watch agent pages repaint and open external links in native Mac tabs that remain with their window across chat switches." (#140988, #141031) Native WebKit Mac tabs in the same Browser panel — they belong to the window and survive chat switches. 5. Connected account management in Models settings: "manage connected accounts and supported account priority directly in Models settings." (#132451) 6. Share selected conversations: "explicitly publish a revocable read-only view of a session's existing and future conversation text, accessible to anyone with its public link." (#139489) 7. Searchable meeting library: "browse saved notes, search full transcripts, download complete Markdown or JSONL archives, and manage capture sources from the Control UI." (#139875, #140084) 8. Optional Team Reports add-on: "install and enable Team Reports to browse authenticated GitHub activity and explicitly configured Discord discussion, with stored history and optional model summaries." (#139850, #141327)
Six Breaking changes the September 8 pillar did not surface:
1. Node runtime — this is the operational hazard. From the v2026.9.3 release notes verbatim: "Breaking — Node runtime: require Node 24.16.0 or newer on 24.x, or Node 26.1.0 or newer; Node 26 is recommended. Upgrade Node before OpenClaw to prevent SQLite text truncation: Node 22, Node 25, and earlier 24.x/26.x builds are no longer supported. Node-based CLI/Gateway installs on macOS 11–13.4 or official Linux ARMv7 provisioning need a supported host." (#140672) The SQLite text-truncation warning matters: a Node 22 install that upgrades to v2026.9.3 without first upgrading Node will silently drop text from SQLite-backed fields. This is a data-integrity hazard, not a crash. 2. Execution-policy SDK: "move the retired exec-mode and comparator helpers from infra-runtime to execPolicy on openclaw/plugin-sdk/agent-harness-runtime; use resolveExecModePolicy and select the returned fields needed by the caller." 3. Approval SDK: "import approval account-resolution helpers from approval-native-runtime, adapt session filtering to the full matchesApprovalRequestFilters contract, and replace the retired generic forwarding evaluator with native channel route gates and shared predicates rather than assuming a drop-in alias." 4. SDK aliases: "replace channel-inbound.buildChannelTurnMediaPayload with buildChannelInboundMediaPayload; infer the retained abortAndDrainAgentHarnessRun callable's result instead of importing the removed AbortAndDrainAgentHarnessRunResult named type. The callable and its result data remain available." 5. Search result callbacks: "read bounded Find/Grep text from details.content instead of details.truncation.content; the outer tool-message content remains unchanged." (#140008) 6. Directory result callbacks: "use LsToolDetails.content and optional nextAfter in place of the retired truncation and entryLimitReached fields, and pass nextAfter as after to continue listing."
The Node runtime change is the only one with a non-plugin, non-developer user impact. The five SDK changes only affect plugin authors; consumers of stock OpenClaw see no behavioral change.
Node 22 / Node 25 / earlier 24.x / earlier 26.x is no longer supported. Any OpenClaw install still on Node 22 needs a Node upgrade before bumping OpenClaw to v2026.9.3 or later. v2026.9.4's "Node runtime recovery" feature exists specifically to help operators through this transition. The September 8 article did not document this; readers following the September 8 article who bumped their OpenClaw on Node 22 are now at risk of SQLite text truncation. If you've already bumped, audit your SQLite-backed fields (conversation history, team memory, plugin state) for truncated or missing text and verify your pre-upgrade backup.
Plugin authors have three SDK breaking changes to plan around. If you maintain a custom plugin that uses the infra-runtime exec-mode helpers, the approval forwarding evaluator, the buildChannelTurnMediaPayload alias, or the removed AbortAndDrainAgentHarnessRunResult type, your plugin will need a patch before v2026.9.3+. The new SDK surfaces are documented in the SDK migration guide linked from each breaking change.
Failed-update recovery is now a real path, with a real boundary. v2026.9.3's safer-updates rehearsal (#138839 et al.) plus v2026.9.4's automatic rollback (#140339) means a failed package update can roll back automatically when the schema and configuration checks prove rollback is safe. The boundary: changed database schemas, incompatible new databases, or intervening operator configuration edits block automatic rollback. A recovered update remains a failed update with a recorded rollback outcome. Database migrations still require a verified pre-update backup. If you've been waiting for OpenClaw to ship "atomic update" semantics before you automate rollouts, v2026.9.4 is the release that delivers most of the value, with the explicit boundary that destructive migrations are out of scope.
GPT Image 2.5 lands in the OpenClaw image picker. v2026.9.4 (#143068, #143069) ships GPT Image 2.5 Flare and Sunburst as selectable variants through OpenAI or fal without changing the default model. The story-2026-09-08 GPT Image 2.5 coverage focused on the Responses API integration; the OpenClaw side gets the picker integration here.
Skill Workshop is now a persistent, agent-owned collection. v2026.9.3 #135528 et al. moves skills to a per-agent writable Workshop collection. The v2026.9.3 release also retires skills.workshop.allowSymlinkTargetWrites. Startup and openclaw doctor --fix migrate proven legacy skills; ambiguous ownership remains in place for review. Plugin authors who depended on workspace-scoped workshop skills should audit their setups before the migration runs.
Primary sources verified at 2026-09-11 12:10 UTC:
tag/v2026.9.4 updated 2026-09-11T07:22:21Z; tag/v2026.9.3 updated 2026-09-08T19:18:34Z; tag/v2026.6.35 updated 2026-09-10T06:43:04Z.No firsthand test was run against either v2026.9.3 or v2026.9.4. The article documents verbatim primary-source claims and is a documentation comparison, not a benchmark or field report.
Cost. No API pricing changes, no metered-service changes, no new subscription tier. The unified Plugins workspace, prepared cloud sessions, and automatic rollback are operational improvements with no documented per-call cost change. The cloud ready workers feature notes that ready workers incur provider running-machine charges until deleted; teams adopting prepared cloud sessions should expect a small increase in cloud-VM spend proportional to the reserve target.
Risk. Two risks to flag operationally:
Limitations.
skills.workshop.allowSymlinkTargetWrites. Operators who relied on symlinked skill targets must audit before the migration runs; ambiguous ownership remains in place for review per the release notes.OpenClaw shipped two substantive releases in three days. v2026.9.4 closes the loop on v2026.9.3's safer-updates foundation with automatic rollback, ships a unified Plugins workspace, prepared cloud sessions, GPT Image 2.5 in the picker, voice that returns delegated subagent results to Talk, and a read-only deployments mode for hosts that want pinned configuration. v2026.9.3 dropped Node 22 / Node 25 / earlier 24.x / earlier 26.x from the supported matrix with a SQLite text-truncation warning, introduced Skill Workshop as a persistent agent-owned collection, and shipped five SDK breaking changes plugin authors need to track.
The September 8 pillar was incomplete on v2026.9.3. Today's pillar is the missing half — eight Highlights + six Breaking changes — plus v2026.9.4. The Node 22 EOL is the most urgent operational signal; teams still on Node 22 should upgrade Node first, then bump OpenClaw to v2026.9.3 or v2026.9.4. Teams already on a supported Node line should consider v2026.9.4 for the automatic-rollback story; teams maintaining custom plugins should audit against the three SDK breaking changes before deploying v2026.9.3 to consumers.
Today
node --version). Node 22.x, Node 25.x, earlier 24.x (before 24.16.0), and earlier 26.x (before 26.1.0) are no longer supported as of v2026.9.3. Upgrade Node first, then bump OpenClaw. Node 24.16.0+ on 24.x, or Node 26.1.0+ on 26.x, are supported. Node 26 is recommended.This week
cloudWorkers.prefiles.<id>.readyWorkers and cloudWorkers.preparedPool.maxTotal to the smallest reserve target that meets your workflow. Ready workers incur provider running-machine charges until deleted; capping the reserve is the only cost lever.skills.workshop.allowSymlinkTargetWrites is retired; ambiguous ownership remains in place for review.Skip if not in scope
Originally published: 2026-09-11 12:08 UTC Last verified: 2026-09-11 12:10 UTC No corrections at this time.
This pillar repays editorial debt from the September 8 v2026.9.3 article. The September 8 article is not retracted; it is now the "fix items" half of the v2026.9.3 picture, and this pillar is the "Highlights + Breaking changes + v2026.9.4" half.