OpenClaw Updates & Release Notes

OpenClaw Oct 18, 2026Update

OpenClaw 2026.10.5 makes conversations restart-safe and lets updates finish themselves

OpenClaw's stable v2026.10.5 makes conversations survive a Gateway restart: interrupted turns, first messages sent during worktree prep, subagent work and deferred tasks all resume where they left off. `openclaw update` now finishes and recovers on its own across devices, filesystems, pnpm 12, Windows elevation and macOS login shells. Also in the release: a channel plugin that answers X mentions, Gemini 4 Argon and Gemini 3.8 Flash in the model pickers, and a one-command Docker quickstart (gateway + Postgres + admin UI, PowerShell variant for Windows).

Your move: Interrupted turns, subagent work and deferred tasks resume after a Gateway restart; updates self-recover; X-mentions plugin; Docker quickstart

OpenClaw's stable v2026.10.5 makes conversations survive a Gateway restart: interrupted turns, first messages sent during worktree prep, subagent work and deferred tasks all resume where they left off. `openclaw update` now finishes and recovers on its own across devices, filesystems, pnpm 12, Windows elevation and macOS login shells. Also in the release: a channel plugin that answers X mentions, Gemini 4 Argon and Gemini 3.8 Flash in the model pickers, and a one-command Docker quickstart (gateway + Postgres + admin UI, PowerShell variant for Windows).

Why it matters

Always-on agents live or die on reliability, and losing a conversation to a restart was OpenClaw's sharpest edge. Restart-safe sessions plus self-healing updates remove the two most common babysitting jobs for self-hosted setups. The rest is routine.

GitHub

OpenClaw Oct 12, 20262026.10.2

OpenClaw 2026.10.2 fixes upgrades from 10.1 and credential redaction

OpenClaw released the stable 2026.10.2 patch on October 12. It fixes the first upgrade from 2026.10.1, successful updates incorrectly ending in errors, and update paths on Windows and some other setups that stalled or rolled back. It also fixes credentials escaping masking when they cross a chunk boundary in long tool output, and makes redaction of large text faster and more reliable. OpenAI and Anthropic API-key routes now use provider-native compaction by default.

Your move: Update for safer upgrades and better masking of credentials in long tool output

OpenClaw released the stable 2026.10.2 patch on October 12. It fixes the first upgrade from 2026.10.1, successful updates incorrectly ending in errors, and update paths on Windows and some other setups that stalled or rolled back. It also fixes credentials escaping masking when they cross a chunk boundary in long tool output, and makes redaction of large text faster and more reliable. OpenAI and Anthropic API-key routes now use provider-native compaction by default.

Why it matters

If you upgraded to 10.1, had trouble updating, or use tools that can return credentials, this patch is worth installing. It also fixes scheduled runs losing tool access and problems with replies being lost or truncated. These are targeted reliability and security fixes, not a promise that every update or secret-handling path is now safe.

GitHub Releases

OpenClaw Oct 10, 20262026.10.1

OpenClaw 2026.10.1 improves MCP Apps and keeps Code Mode values across restarts

OpenClaw published the stable 2026.10.1 release on October 10. MCP Apps can call their tools while their views remain open, with inline message confirmations and synchronized forms, files and context. Code Mode's store/load values now remain available across cells, replies and Gateway restarts. The release also fixes problems with updates, session continuation, model responses and message delivery.

Your move: A stable release focused on app interaction, saved working values and reliability

OpenClaw published the stable 2026.10.1 release on October 10. MCP Apps can call their tools while their views remain open, with inline message confirmations and synchronized forms, files and context. Code Mode's store/load values now remain available across cells, replies and Gateway restarts. The release also fixes problems with updates, session continuation, model responses and message delivery.

Why it matters

For people who use MCP Apps or work through a task in several Code Mode steps, this makes the agent's workspace more useful and less fragile. The reliability fixes matter for self-hosted setups, but this is mostly an improvement to existing workflows rather than a new autonomous capability.

GitHub Releases

OpenClaw Oct 3, 20262026.9.8

OpenClaw 2026.9.8 adds GPT-6.1 Sol

OpenClaw published 2026.9.8 on October 3, 2026. It adds GPT-6.1 Sol on the OpenAI provider for accounts that have access to it, and keeps delegated results on the conversation that asked for them. The release also fixes failed updates and Windows startup problems.

Your move: For OpenAI accounts that already have GPT-6.1 Sol

OpenClaw published 2026.9.8 on October 3, 2026. It adds GPT-6.1 Sol on the OpenAI provider for accounts that have access to it, and keeps delegated results on the conversation that asked for them. The release also fixes failed updates and Windows startup problems.

Why it matters

If your OpenAI account already has GPT-6.1 Sol, update to use it in OpenClaw. The same update is worth installing if a recent upgrade failed or OpenClaw has trouble starting on Windows.

GitHub Releases

OpenClaw Oct 2, 20262026.8.35

OpenClaw 2026.8.35 brings GPT-6.1 Sol to the extended-stable line

OpenClaw released v2026.8.35 on October 2, 2026, a gateway-only update on its extended-stable branch, the project's long-term-support-style track. The highlight is GPT-6.1 Sol, plus safer updates and fixes so delegated replies stay complete. The release notes say this line is the August 2026 release plus later fixes, and that mainline was already on 2026.9.7 when this cut went out.

Your move: Affects the extended-stable (LTS-style) line, not the 2026.9.x releases

OpenClaw released v2026.8.35 on October 2, 2026, a gateway-only update on its extended-stable branch, the project's long-term-support-style track. The highlight is GPT-6.1 Sol, plus safer updates and fixes so delegated replies stay complete. The release notes say this line is the August 2026 release plus later fixes, and that mainline was already on 2026.9.7 when this cut went out.

Why it matters

If you self-host OpenClaw on the extended-stable track rather than the faster-moving 2026.9.x line, this is how you get GPT-6.1 Sol without leaving that track. If you are already on 2026.9.x, this release does not apply to you.

GitHub Releases

OpenClaw Sep 30, 20262026.9.7

OpenClaw 2026.9.7 adds the OpenAI Agents API and Sign in with ChatGPT

OpenClaw 2026.9.7 came out on September 30, 2026. It is snappier under load and smoother in long conversations, and update recovery is safer, with better backups and rollback. The release also adds the OpenAI Agents API and Sign in with ChatGPT (beta).

Your move: Snappier under load, with safer recovery if an update fails

OpenClaw 2026.9.7 came out on September 30, 2026. It is snappier under load and smoother in long conversations, and update recovery is safer, with better backups and rollback. The release also adds the OpenAI Agents API and Sign in with ChatGPT (beta).

Why it matters

If you self-host OpenClaw and use OpenAI, this update adds a way to run agents through OpenAI's Agents API and a beta option to sign in with a ChatGPT account. Update to get both, along with safer recovery when an update fails.

GitHub Releases

OpenClaw Sep 29, 2026Enterprise

OpenClaw announces a free control plane for persistent agents

OpenClaw announced OpenClaw Enterprise on September 29, 2026, a free MIT-licensed control plane for running persistent agents on your own servers, with separate team spaces, sandboxes, and an audit log. The work started at OpenAI, then moved to the OpenClaw Foundation, and Red Hat and NVIDIA are helping build it. It is meant for internal pilots, with a 1.0 release planned later this year.

Your move: Free to self-host, still a pilot before version 1.0

OpenClaw announced OpenClaw Enterprise on September 29, 2026, a free MIT-licensed control plane for running persistent agents on your own servers, with separate team spaces, sandboxes, and an audit log. The work started at OpenAI, then moved to the OpenClaw Foundation, and Red Hat and NVIDIA are helping build it. It is meant for internal pilots, with a 1.0 release planned later this year.

Why it matters

If your company wants OpenClaw agents but needs shared security, permissions, and an audit log, this is the build for that. It is early, so the current use is a self-hosted pilot.

OpenClaw

OpenClaw Sep 24, 2026v2026.9.6

OpenClaw replaces a 2026.9.6 Mac build that crashed on launch

OpenClaw's 2026.9.6 release shipped a macOS build on September 23, 2026 that crashed immediately on launch. The next day, the team replaced it with a rebuilt, notarized version of the same 2026.9.6 DMG that fixes the crash. The npm package was never affected, only the standalone Mac app download.

Your move: Reinstall the new Mac build if 2026.9.6 won't open

OpenClaw's 2026.9.6 release shipped a macOS build on September 23, 2026 that crashed immediately on launch. The next day, the team replaced it with a rebuilt, notarized version of the same 2026.9.6 DMG that fixes the crash. The npm package was never affected, only the standalone Mac app download.

Why it matters

If you installed 2026.9.6 on a Mac and the app won't open, download the new DMG, or update through the app from 2026.9.5, to get a working copy. Windows and Linux users, and anyone running OpenClaw through npm, were not affected.

OpenClaw release notes

OpenClaw Sep 23, 20262026.9.6

OpenClaw 2026.9.6 shipped with a Mac build that crashed on launch

OpenClaw released version 2026.9.6 on September 23, 2026, adding clearer messages about what an update actually did, recovery of unfinished work after a restart, 30 days of usage reporting, a GitHub reader inside chat, and support for newer chat models including Claude Opus 5.5, GPT-6, and Grok 4.7. The first Mac app build in this release crashed every time it launched for many users, so OpenClaw pulled it from the automatic update feed. A fixed, working build went out the next day, September 24. The npm and Gateway package version of 2026.9.6 was not affected by the crash.

Your move: If your Mac app stopped opening after updating, reinstall the fixed build by hand

OpenClaw released version 2026.9.6 on September 23, 2026, adding clearer messages about what an update actually did, recovery of unfinished work after a restart, 30 days of usage reporting, a GitHub reader inside chat, and support for newer chat models including Claude Opus 5.5, GPT-6, and Grok 4.7. The first Mac app build in this release crashed every time it launched for many users, so OpenClaw pulled it from the automatic update feed. A fixed, working build went out the next day, September 24. The npm and Gateway package version of 2026.9.6 was not affected by the crash.

Why it matters

If you use OpenClaw's Mac app and it stopped opening after this update, the automatic updater can't fix an app that already won't launch: download the new build from OpenClaw's GitHub releases page and reinstall it by hand. Everyone else, and anyone who hasn't updated yet, can install 2026.9.6 as normal now that the fix is out.

GitHub Releases

OpenClaw Sep 21, 2026Security audit

An outside audit finds and fixes two high-severity bugs in OpenClaw

OpenClaw had its code audited by security firm Trail of Bits, through OpenAI's "Patch the Planet" program. The audit turned up 27 issues: 2 rated high severity, 16 medium, 6 low, and 3 "defense in depth" suggestions that didn't cross a real security boundary. Nothing was rated critical. OpenClaw says every issue has already been fixed and merged into the project.

Your move: Every flagged issue is already patched, nothing for users to do

OpenClaw had its code audited by security firm Trail of Bits, through OpenAI's "Patch the Planet" program. The audit turned up 27 issues: 2 rated high severity, 16 medium, 6 low, and 3 "defense in depth" suggestions that didn't cross a real security boundary. Nothing was rated critical. OpenClaw says every issue has already been fixed and merged into the project.

Why it matters

Nothing is broken and there's no update to install just for this. It's still worth knowing that an outside firm looked closely at OpenClaw's code and found real, if not critical, security bugs, and that the project fixed them before they became a problem for users.

OpenClaw Blog

OpenClaw Sep 21, 20262026.7.35

OpenClaw's extended-stable line fixes a bug that could wipe bundled plugins

OpenClaw released v2026.7.35 on its extended-stable branch, the project's long-term-support-style track, on September 21, 2026. It fixes a bug where running the built-in Doctor repair tool could wipe out bundled plugins, including Browser, Canvas, pairing, file-transfer, phone-control, Talk voice, and Bonjour, so they didn't come back after a restart. The release also automatically recovers from a partially broken plugin registry left behind by the earlier 2026.7.34 build. OpenClaw says installs will heal existing broken registries automatically on upgrade.

Your move: Affects the extended-stable (LTS-style) line, not the 2026.9.x releases

OpenClaw released v2026.7.35 on its extended-stable branch, the project's long-term-support-style track, on September 21, 2026. It fixes a bug where running the built-in Doctor repair tool could wipe out bundled plugins, including Browser, Canvas, pairing, file-transfer, phone-control, Talk voice, and Bonjour, so they didn't come back after a restart. The release also automatically recovers from a partially broken plugin registry left behind by the earlier 2026.7.34 build. OpenClaw says installs will heal existing broken registries automatically on upgrade.

Why it matters

If you self-host OpenClaw on the extended-stable track rather than the faster-moving 2026.9.x line, and you've run Doctor to repair your install, you could have silently lost core plugins. Update to this release, since it fixes the bug going forward and also repairs existing broken installs.

Official release notes

OpenClaw Sep 19, 20262026.9.5

OpenClaw 2026.9.5 upgrades its database and requires a backup first

OpenClaw 2026.9.5, released September 19, 2026, upgrades agent databases to a new schema (schema 21) that older builds can't open. The release notes say to make and verify a backup before upgrading: going back afterward means restoring that backup with the matching older build, since reinstalling an older package alone won't undo it. Anyone updating from 2026.9.2 needs to follow a separate manual schema-upgrade step. The release also adds "Atomic Updates" that check the next version before switching over, lets you install or reload plugins without restarting the Gateway, and now asks for your explicit "Yes" before its AI-based triage agent tries to repair a failed update, instead of running on its own.

Your move: Back up before you update; older builds can't open the new database

OpenClaw 2026.9.5, released September 19, 2026, upgrades agent databases to a new schema (schema 21) that older builds can't open. The release notes say to make and verify a backup before upgrading: going back afterward means restoring that backup with the matching older build, since reinstalling an older package alone won't undo it. Anyone updating from 2026.9.2 needs to follow a separate manual schema-upgrade step. The release also adds "Atomic Updates" that check the next version before switching over, lets you install or reload plugins without restarting the Gateway, and now asks for your explicit "Yes" before its AI-based triage agent tries to repair a failed update, instead of running on its own.

Why it matters

If you self-host OpenClaw, back up your database before installing this update, not after. Going back to an older version isn't as simple as reinstalling the old package once you've upgraded, so this is a real one-way step if you skip the backup.

Official release notes

OpenClaw Sep 11, 20262026.9.4

OpenClaw 2026.9.4 adds automatic rollback for failed updates

OpenClaw 2026.9.4, released on September 11, 2026, can now recover on its own from a failed update by restoring the previous version and configuration when it's safe to do so. Database migrations still need a verified backup first. The release also adds one Control UI screen for finding and installing both bundled and ClawHub plugins, and a new admin option to lock configuration to read-only so it can't be rewritten by mistake.

Your move: Update for safer self-hosted upgrades and easier plugin setup

OpenClaw 2026.9.4, released on September 11, 2026, can now recover on its own from a failed update by restoring the previous version and configuration when it's safe to do so. Database migrations still need a verified backup first. The release also adds one Control UI screen for finding and installing both bundled and ClawHub plugins, and a new admin option to lock configuration to read-only so it can't be rewritten by mistake.

Why it matters

Since OpenClaw runs on your own machine or server, a broken update used to mean fixing it yourself. Automatic rollback removes most of that risk, and the read-only config lock helps admins running OpenClaw across a team keep settings from drifting. If you self-host OpenClaw, updating gets you safer upgrades with less manual cleanup.

GitHub release notes

OpenClaw Sep 10, 2026v2026.6.35

OpenClaw closes out its June LTS line with a security and reliability patch

OpenClaw shipped v2026.6.35, the final Extended Stable release for its June 2026 line, covering 166 merged pull requests since the last patch. It tightens limits on how much data providers and channels will read from a response, so a hostile server can't exhaust memory, and rejects oversized or malformed inputs before they can interrupt an agent run. It also makes retries and dropped connections safer, so long-running jobs don't lose work or repeat an unsafe action after a failure.

Your move: Only matters if you're still on the 2026.6.x line; mainline is already past this

OpenClaw shipped v2026.6.35, the final Extended Stable release for its June 2026 line, covering 166 merged pull requests since the last patch. It tightens limits on how much data providers and channels will read from a response, so a hostile server can't exhaust memory, and rejects oversized or malformed inputs before they can interrupt an agent run. It also makes retries and dropped connections safer, so long-running jobs don't lose work or repeat an unsafe action after a failure.

Why it matters

OpenClaw's main releases have moved on to the 2026.9.x line, but this patch is the last word on the older 2026.6.x branch that some self-hosted setups still run. If you're on that branch, update now to pick up the security backports. If you're already on 2026.9.x, this release doesn't apply to you.

GitHub Releases

OpenClaw Sep 9, 2026SDK deprecation notice

OpenClaw plugin SDK marks an old credential-prompt style as deprecated

On September 9, 2026, OpenClaw marked an old way of calling `buildCredentialSafetyPrompt` in its plugin SDK as deprecated. That function builds the message a plugin shows when it needs to ask for a login. The old style passed it a plain block of text; the new style passes it a settings object instead. The old style still works today and isn't being removed yet.

Your move: Old plugins keep working through November 30, 2026

On September 9, 2026, OpenClaw marked an old way of calling `buildCredentialSafetyPrompt` in its plugin SDK as deprecated. That function builds the message a plugin shows when it needs to ask for a login. The old style passed it a plain block of text; the new style passes it a settings object instead. The old style still works today and isn't being removed yet.

Why it matters

This only affects people who write or maintain OpenClaw plugins that ask users to log in. The old format keeps working through November 30, 2026, so nothing breaks right away, but plugin authors should switch to the new settings-object style before it's eligible for removal on December 1, 2026.

OpenClaw Docs

OpenClaw Sep 8, 20262026.9.3

OpenClaw 2026.9.3 raises the minimum Node.js version and changes SDK callbacks

OpenClaw 2026.9.3 came out on September 8, 2026. It now needs Node.js 24.16.0 or newer, or 26.1.0 or newer, so some setups will need a Node upgrade before they can install it. The release also changes how the approval, execution-policy, and search-result callbacks work in the OpenClaw SDK, and skills built in Workshop now live in one shared collection tied to the agent instead of belonging to a single workspace. Updates are safer too: the app now tests core and plugin changes in an isolated state before turning them on, and can recover better if an update gets interrupted. Other additions include publishing a chat as a read-only link you can revoke later, and a meeting library for searching saved call transcripts and downloading them as Markdown or JSONL.

Your move: Check your Node.js version and any custom SDK code before updating

OpenClaw 2026.9.3 came out on September 8, 2026. It now needs Node.js 24.16.0 or newer, or 26.1.0 or newer, so some setups will need a Node upgrade before they can install it. The release also changes how the approval, execution-policy, and search-result callbacks work in the OpenClaw SDK, and skills built in Workshop now live in one shared collection tied to the agent instead of belonging to a single workspace. Updates are safer too: the app now tests core and plugin changes in an isolated state before turning them on, and can recover better if an update gets interrupted. Other additions include publishing a chat as a read-only link you can revoke later, and a meeting library for searching saved call transcripts and downloading them as Markdown or JSONL.

Why it matters

If you run OpenClaw on an older Node.js version, or you built anything against its SDK using the old approval, execution-policy, or search-result callbacks, check your setup before updating: this release breaks both. Everyone else mainly gets safer updates and a couple of smaller additions.

GitHub Releases

OpenClaw Sep 5, 20262026.9.2

OpenClaw 2026.9.2 turns on multi-agent swarms by default and speeds up chat

OpenClaw 2026.9.2 came out on September 5, 2026. Chat feels faster because loading long conversation history and cleaning up disk space now happen separately from the live chat instead of blocking it. The release also turns on "swarm" mode by default, so multiple sub-agents can work on a task at the same time, though it still respects anyone who had already turned that off. It adds support for OpenAI's new GPT-6 Astra model with text and image input, lets more settings change without restarting the whole system, and fixes a backup bug that could corrupt saved text containing certain special characters. The release includes 1,247 merged pull requests.

Your move: Swarm mode is now on unless you already turned it off

OpenClaw 2026.9.2 came out on September 5, 2026. Chat feels faster because loading long conversation history and cleaning up disk space now happen separately from the live chat instead of blocking it. The release also turns on "swarm" mode by default, so multiple sub-agents can work on a task at the same time, though it still respects anyone who had already turned that off. It adds support for OpenAI's new GPT-6 Astra model with text and image input, lets more settings change without restarting the whole system, and fixes a backup bug that could corrupt saved text containing certain special characters. The release includes 1,247 merged pull requests.

Why it matters

If you rely on OpenClaw running single-agent for predictability, check your settings after updating: swarm mode is now the default, not something you have to turn on. Everyone else gets a faster, more reliable app and a new model option for free.

GitHub Releases

OpenClaw Sep 3, 2026AgentCore Payments

OpenClaw agents can now make bounded payments through AWS

AWS's AgentCore Payments went generally available on August 18, 2026. On September 3, OpenClaw added support for it, so OpenClaw agents can now use AWS's aws-agents-pay plugin to make bounded, human-approved payments for paywalled APIs, MCP servers, and other paid web content.

Your move: For paywalled APIs, MCP servers, and web content

AWS's AgentCore Payments went generally available on August 18, 2026. On September 3, OpenClaw added support for it, so OpenClaw agents can now use AWS's aws-agents-pay plugin to make bounded, human-approved payments for paywalled APIs, MCP servers, and other paid web content.

Why it matters

If your OpenClaw agent regularly hits paywalls or paid APIs while working, this gives it a supervised way to pay for access itself instead of you stepping in each time. It still requires your approval for each payment, so it's not something to enable and forget.

X

OpenClaw Sep 3, 20262026.9.1

OpenClaw 2026.9.1 adds Mermaid diagrams and lighter long chats

OpenClaw 2026.9.1 came out on September 3, 2026. It can now render Mermaid diagrams in chat, setup skips unnecessary steps, updates know when it's safe to apply themselves, and long chat histories load lighter than before. The release includes 1,186 merged pull requests and 28 direct commits from 281 contributors.

Your move: 1,186 merged pull requests from 281 contributors

OpenClaw 2026.9.1 came out on September 3, 2026. It can now render Mermaid diagrams in chat, setup skips unnecessary steps, updates know when it's safe to apply themselves, and long chat histories load lighter than before. The release includes 1,186 merged pull requests and 28 direct commits from 281 contributors.

Why it matters

If you use OpenClaw for anything involving diagrams or flowcharts, or you keep long-running chat histories, this update should make both noticeably better. Update to get it.

X

OpenClaw Sep 1, 20262026.8.2

OpenClaw finally ships a real Linux desktop app

OpenClaw 2026.8.2 came out on September 1, 2026. It adds Quick Chat, a small chat bar you can summon with Ctrl+Shift+Space on X11 or from the tray icon (global shortcuts aren't available on Wayland, so it's tray-only there), a real Linux app instead of just a browser tab, and safer updates, so your settings won't get wiped and a bad update won't break a running agent.

Your move: Update now for native Linux support and safer upgrades

OpenClaw 2026.8.2 came out on September 1, 2026. It adds Quick Chat, a small chat bar you can summon with Ctrl+Shift+Space on X11 or from the tray icon (global shortcuts aren't available on Wayland, so it's tray-only there), a real Linux app instead of just a browser tab, and safer updates, so your settings won't get wiped and a bad update won't break a running agent.

Why it matters

If you run OpenClaw as an always-on agent, this update matters: it brings proper Linux support and fixes the update problems that used to risk losing your settings or breaking your setup.

GitHub Releases

OpenClaw Aug 31, 20262026.8.1

OpenClaw 2.0 ships masked credentials and session permission controls

OpenClaw shipped version 2026.8.1, called OpenClaw 2.0, on August 31, 2026. It's the biggest release yet, with 933 contributors and over 16,000 merged changes after a two-month pause in updates. Among the highlights: your agent can now request a credential through a masked prompt that never puts its value in chat or model context, new session permission modes control filesystem access, sessions can now run on paired devices or cloud workers so you can collaborate, you can search past conversations by exact words or phrases, and the release includes general startup speed improvements.

Your move: The bigger release before the Sep 1 patch you already saw

OpenClaw shipped version 2026.8.1, called OpenClaw 2.0, on August 31, 2026. It's the biggest release yet, with 933 contributors and over 16,000 merged changes after a two-month pause in updates. Among the highlights: your agent can now request a credential through a masked prompt that never puts its value in chat or model context, new session permission modes control filesystem access, sessions can now run on paired devices or cloud workers so you can collaborate, you can search past conversations by exact words or phrases, and the release includes general startup speed improvements.

Why it matters

The masked credential requests and session permission modes are the biggest security-relevant changes OpenClaw has shipped. They matter most if you run OpenClaw with access to real accounts or sensitive files. The Sep 1 update already on this log was just a smaller patch on top of this release, not the main event.

Official release notes

OpenClaw

Latest on OpenClaw