What breaks when I upgrade to OpenClaw 2026.9.2?

OpenClaw 2026.9.2 changes session-tool defaults so agents can read other agents' conversations, deprecates the `messages.suppressToolErrors` setting, and needs legacy `channel:user:id` owner identities repaired. Running `openclaw doctor --fix` migrates the deprecated settings and legacy owner entries. The 'Add to Workboard' actions were also removed from chat headers and session menus.

How do I stop OpenClaw agents from reading each other's conversations?

Set `tools.sessions.visibility` to `agent` or `self` in OpenClaw 2026.9.2. The release changed the default to all-session visibility with ordinary agent-to-agent access enabled, so anyone running a shared Gateway should review conversation access before upgrading. Existing tool and sandbox restrictions still apply on top of whichever visibility level you pick.

Which new models does OpenClaw 2026.9.2 add?

OpenClaw 2026.9.2 adds OpenAI's GPT-6 Astra, selectable as `openai/gpt-6-astra` with text and image input, Responses tool calls and supported reasoning controls, plus Meta's Muse Spark 1.3. Subscription availability for Astra follows successful ChatGPT or Codex account discovery; an OpenAI API-key profile works either way.

Do I still need to restart the OpenClaw Gateway to change settings?

Far less often. OpenClaw 2026.9.2 applies agent, model, tool, channel, browser, node, access and terminal settings through their running owners instead of requiring a restart. Settings that genuinely still need a Gateway restart stay marked in the configuration reference. On Linux without a service manager, upgrading from v2026.8.2 uses `openclaw update --no-restart`.

What changes now that OpenClaw swarm is on by default?

Swarm lets OpenClaw orchestrate concurrent sub-agents and return structured results with live progress, and 2026.9.2 makes that the default behaviour. Explicit opt-outs and tool restrictions are preserved, and the separate Code Mode opt-in is unchanged, so a Gateway that already disabled swarm keeps its setting through the upgrade.

OpenClaw · 2026-09-05 · major

OpenClaw 2026.9.2 — GPT-6 Astra support and swarms on by default

OpenClaw 2026.9.2 adds GPT-6 Astra and Muse Spark 1.3, turns sub-agent swarms on by default, and applies most settings without a Gateway restart. Session tools now let agents read each other's conversations unless you narrow them.

OpenClaw v2026.9.2 release page on GitHub

OpenClaw's September release picks up GPT-6 Astra on day one and switches concurrent sub-agent swarms on for everyone.

Key specs

GitHub stars	389,010

Quick facts

Version	2026.9.2
Released	September 5, 2026
New models	GPT-6 Astra, Muse Spark 1.3
Default change	Swarm sub-agents enabled
Breaking change	Session tools default to all-session visibility
Upgrade step	openclaw doctor --fix
Language	TypeScript

What is it?

GPT-6 Astra can now be selected inside OpenClaw as `openai/gpt-6-astra`, using either an OpenAI API-key profile or an eligible ChatGPT or Codex account, with text and image input and Responses tool calls. Meta's Muse Spark 1.3 arrives in the same release. OpenClaw is the open-source self-hosted assistant that runs agents across chat apps, a browser, and a terminal, and it has 389,010 GitHub stars.

How does it work?

On OpenAI Platform API-key routes that use the official Responses endpoint, OpenClaw 2026.9.2 runs direct function tools asynchronously and steers an active response over a cached WebSocket, so you can redirect a running task instead of cancelling it. A new `/think ultra` setting orchestrates deeper reasoning for both the OpenClaw and the native Codex runtime. Swarm, which fans a job out to concurrent sub-agents and returns structured results with live progress, is on by default.

Why does it matter?

Self-hosters get the newest frontier model without waiting for a vendor app, and the settings work removes a long-standing annoyance: agent, model, tool, channel, browser, node, access, and terminal settings now apply through their running owners rather than forcing a Gateway restart. One change needs care before you upgrade — session tools default to all-session visibility, so an agent with those tools can read other agents' conversations on a shared Gateway.

Who is it for?

self-hosters, agent builders, and teams running a shared OpenClaw Gateway

Frequently asked questions

What breaks when I upgrade to OpenClaw 2026.9.2?: OpenClaw 2026.9.2 changes session-tool defaults so agents can read other agents' conversations, deprecates the `messages.suppressToolErrors` setting, and needs legacy `channel:user:id` owner identities repaired. Running `openclaw doctor --fix` migrates the deprecated settings and legacy owner entries. The 'Add to Workboard' actions were also removed from chat headers and session menus.
How do I stop OpenClaw agents from reading each other's conversations?: Set `tools.sessions.visibility` to `agent` or `self` in OpenClaw 2026.9.2. The release changed the default to all-session visibility with ordinary agent-to-agent access enabled, so anyone running a shared Gateway should review conversation access before upgrading. Existing tool and sandbox restrictions still apply on top of whichever visibility level you pick.
Which new models does OpenClaw 2026.9.2 add?: OpenClaw 2026.9.2 adds OpenAI's GPT-6 Astra, selectable as `openai/gpt-6-astra` with text and image input, Responses tool calls and supported reasoning controls, plus Meta's Muse Spark 1.3. Subscription availability for Astra follows successful ChatGPT or Codex account discovery; an OpenAI API-key profile works either way.
Do I still need to restart the OpenClaw Gateway to change settings?: Far less often. OpenClaw 2026.9.2 applies agent, model, tool, channel, browser, node, access and terminal settings through their running owners instead of requiring a restart. Settings that genuinely still need a Gateway restart stay marked in the configuration reference. On Linux without a service manager, upgrading from v2026.8.2 uses `openclaw update --no-restart`.
What changes now that OpenClaw swarm is on by default?: Swarm lets OpenClaw orchestrate concurrent sub-agents and return structured results with live progress, and 2026.9.2 makes that the default behaviour. Explicit opt-outs and tool restrictions are preserved, and the separate Code Mode opt-in is unchanged, so a Gateway that already disabled swarm keeps its setting through the upgrade.

Try it

openclaw doctor --fix