openclaw 2026.9 update: what's new and should you update
OpenClaw 2026.9.2 landed on npm September 5, five days after 2026.8.2. The features with headlines: settings that apply without a Gateway restart, replies that survive one, backups that refuse corrupt archives, and GPT-6 Astra as a selectable model. The two changes most likely to affect you got no headline at all — Swarm is now on by default, and your agents can read each other’s sessions.
Start with the shipping pace, because it explains everything else.
| version | published | what you’d actually notice |
|---|---|---|
| 2026.8.2 | September 1 | Home agent in a side dock, Linux desktop app (.deb/AppImage), background sessions from New Session |
| 2026.9.1 | September 3 | Mermaid diagrams render in chat, one-prompt fresh install, personal skill libraries, updates that roll themselves back |
| 2026.9.2 | September 5 | live settings without restart, restart-proof replies, GPT-6 Astra, Swarm on by default |
Three stable releases in five days. That is the actual product decision behind this update, and every judgment below follows from it.
what’s new in openclaw 2026.9.1
The one you’ll see immediately is Mermaid rendering. Diagram blocks now draw as diagrams in the Control UI and in the macOS, iOS, and Android apps, with enlarge previews. Ask an agent to explain your infrastructure and you get a picture instead of a fenced code block you have to paste somewhere else.
Fresh installs got a quick-start lane. npx openclaw@latest now detects existing Claude Code or Codex logins and API keys, verifies them live, and opens the web dashboard from a foreground Gateway. The full wizard is still there as Custom setup. This is the fix for the single biggest complaint about self-hosted agents: the empty terminal after install.
Personal skill libraries (openclaw skills library) let you keep your own skills next to the shared workspace set on a team Gateway, import them from ZIP archives, and publish per identity. If you’ve been the person whose useful skill lived in a gist because the shared library was someone else’s turf, this is your release.
The part nobody screenshots but everybody needed: openclaw update now rolls back the npm candidate when the post-update Doctor fails, preserves your config and secret references across a failed upgrade, and hands the failure to a built-in triage agent. Alongside it, the Gateway got harder to kill on boot — malformed legacy cron rows are quarantined instead of blocking startup, and migration warnings degrade the Gateway rather than refusing to start it.
Three config knobs from 9.1 are worth stealing even if you skip the rest: blockedHostnames on the SSRF policy blocks configured hosts for browser, web fetch, and webhooks; cron.skipMissedJobs stops the thundering herd of missed recurring jobs at startup; and openclaw memory reset rebuilds derived indexes without deleting sessions, which is the command people used to approximate by nuking state.
what’s new in openclaw 2026.9.2
Settings apply without a Gateway restart. Agent, model, tool, channel, browser, node, access, and terminal settings now go through their running owners. The settings that still need a restart stay marked in the configuration reference, which is the honest way to ship this — a blanket “no more restarts” claim would have been a lie by the second edge case.
Replies survive restarts. Active, queued, and delegated replies recover after the Gateway comes back, and continuation instructions persist through compaction and retries. If you’ve watched a long delegated task evaporate because something bounced the Gateway, that’s the fix.
Backups stopped lying to you. Git backups preserve text containing embedded NUL characters, Nix-managed config and credential links are supported, and corrupt archive headers are now rejected instead of accepted as an incomplete backup. A backup that silently truncates is worse than no backup, because you stop worrying.
GPT-6 Astra is selectable as openai/gpt-6-astra with an OpenAI API-key profile or an eligible ChatGPT/Codex account — text and image input, Responses tool calls, reasoning controls, plus /think ultra orchestration. 9.1 had already added Anthropic Fable 5.1 from shared model metadata.
And chat got faster in the boring, correct way: durable history reads moved outside the Gateway event loop, so long transcripts and disk usage stop blocking your dashboard.
the two defaults that changed without a headline
Both of these live in the “Changes” section of the 2026.9.2 notes, below the highlights, and both change behavior on upgrade.
Swarm is enabled by default. Your agent can now orchestrate concurrent sub-agents with structured results and live progress. Explicit opt-outs, tool restrictions, and the separate Code Mode opt-in are preserved, so nothing you locked down comes unlocked. What does change is spend: concurrent sub-agents mean concurrent token burn, and an agent that used to answer with one model call can now answer with six. If you’re on a metered API key rather than a subscription, look at your usage panel this week, not next month.
Cross-agent session access is on. Session tools now default to all-session visibility, and ordinary agent-to-agent access is enabled. Set tools.sessions.visibility to agent or self if you want the narrow behavior back. Existing tool and sandbox restrictions still apply, so this isn’t a hole — but if you run one Gateway with a work agent and a personal agent, the default just became “they can see each other.” Decide that on purpose.
should you update to openclaw 2026.9.2?
Update if you’re on 2026.8.x and you’ve lost in-flight replies to restarts, fought a failed upgrade, or wanted config changes to take effect without bouncing the Gateway. That’s most people, and the recovery work in 9.1 plus 9.2 is the best argument this release has.
Wait a few days if your Gateway runs headless under a systemd user service. There’s an open regression filed September 7 and labeled P1: after upgrading to 2026.9.2, openclaw gateway restart hangs, because systemd enters deactivating while the existing Node process stays alive and keeps serving on port 18789. The reported workaround is openclaw gateway stop followed by openclaw gateway start, which works normally. It’s one confirmed report with a clean reproduction, not a mass outage — but “restart hangs” is exactly the failure you don’t want to discover during an unattended update.
Two smaller ones from the same day: workspace-relative agent avatars return 401 in the Control UI agent picker, and doctor --fix / gateway status --deep fail with EACCES on systemctl --user is-enabled under a systemd user service. Cosmetic and annoying, respectively.
One upgrade footnote from the 9.1 notes that people keep missing: if you’re on 2026.8.2 without a service manager, run openclaw update --no-restart once. Updates now proceed without a Gateway service instead of refusing outright, and that single flag is the bridge.
what if you want boring instead of weekly?
OpenClaw’s answer is the extended-stable channel: package-only, foreground-only installs, read-only update hints that never apply automatically. You switch with openclaw update --channel extended-stable, or install once with npm install -g openclaw@extended-stable. It was announced as a monthly line, numbered YYYY.M.33, with backported security and reliability fixes bumping the patch and each release supported until the next one is cut.
Here’s the part you should know before you plan around it. As of September 7, 2026, the npm extended-stable selector resolves to 2026.6.34 — the June line, last published August 4. There is no 2026.7.33 on npm and no 2026.8.33. The monthly cadence was described; two months of it haven’t shipped.
That doesn’t make extended-stable useless. A version that sat untouched for a month while stable shipped four releases is, by definition, the well-tested one, and that’s the whole point of the channel. Just don’t choose it expecting a fresh line in October, and don’t expect September’s fixes to be in it. Check what the selector actually resolves to before you pin a fleet to it: npm view openclaw dist-tags.
the deprecation with a date on it
Buried at the bottom of the 2026.9.2 notes: deprecated untrusted-named prompt-context aliases in the Plugin SDK become eligible for removal on or after September 8, 2026. Migrate to the channel-named context fields and buildChannelMetadata. If you maintain an OpenClaw plugin, that date is tomorrow relative to this release, and “eligible for removal” is the phrasing that precedes a plugin that stops loading.
One more piece of trivia that will save someone an afternoon: v2026.9.1-beta.1, published August 28, is not newer than 2026.9.1. The maintainers labeled it themselves — it’s actually 2026.8.1-beta.4, published under the wrong version by mistake, with a warning on the release telling stable users to install 2026.8.1 instead. Version numbers are a promise, and that one bounced.
The pattern across both releases is a project that stopped shipping features at reliability’s expense and started shipping reliability as the feature. Rollback on failed update, replies that outlive a restart, backups that refuse to be half-written, cron rows that can’t brick a boot — none of that demos well, and all of it is what you notice at 3am. The irony is that the release fixing update reliability shipped with a restart bug. Give it a week.