Plugin settings survive update recovery
OpenClaw 2026.9.8 keeps your plugin settings through update recovery
OpenClaw 2026.9.8 is a reliability hotfix, and update recovery now keeps your plugin settings. An incompatible local plugin stays blocked but keeps its settings, so once it's fixed, repair restores it in the same run.
SQLite contention
OpenClaw 2026.9.8Maintenance waits out a briefly locked SQLite database
Plugin updates and Doctor retry the lock and keep their maintenance lease.
Plugin updates and Doctor maintenance could fail when another writer briefly held the SQLite state database. They now wait through that contention and retry, and keep their maintenance lease.
Windows 2026.9.4 schema upgrades
OpenClaw 2026.9.8Unsafe schema upgrades from Windows 2026.9.4 are refused
The update stops before the new package activates.
On Windows, the 2026.9.4 updater could migrate shared state and then fail to read it. OpenClaw now refuses that unsafe schema transition before the new package activates.
Empty Telegram bindings
OpenClaw 2026.9.8An empty Telegram bindings file no longer blocks updates
Doctor archives it once it is verified empty. Files that may hold data still block.
Upgrades from 2026.9.6 could stop on an empty, retired Telegram thread-bindings file. Doctor now archives it once it's verified empty. A file that may still hold your data keeps blocking, untouched.
Doctor on large installs
OpenClaw 2026.9.8Doctor finishes on large installs
Doctor also holds up on large installs. A long chain of session owners no longer overflows the stack, and a big agent fleet no longer exhausts memory during its tool checks.
02: Gateway
OpenClaw 2026.9.8The Gateway.
One Gateway per container
OpenClaw 2026.9.8One Gateway per state directory in containers
A second starter is refused, and the first Gateway keeps running.
Container onboarding could start two Gateways sharing one state directory. Every start now goes through single-owner admission, so a second starter is refused and the first Gateway keeps running.
TLS health checks behind a proxy
OpenClaw 2026.9.8Local TLS health checks work behind a managed proxy
Doctor and restart checks reach the Gateway with the proxy still on.
With a managed HTTP proxy turned on, health checks against a local TLS Gateway used to crash. Doctor and restart checks now reach it with your proxy still enabled.
Windows startup hangs
OpenClaw 2026.9.8Windows startup stops hanging on long temp paths
Past 200 characters, the compile cache is skipped with a warning.
On Windows, a deep temporary directory could make Node's compile-cache path too long, and the command line hung at full CPU. Past 200 characters, OpenClaw now skips that cache and logs a warning.
03: Agents and sessions
OpenClaw 2026.9.8Agents and sessions.
Anthropic turns after background Bash
OpenClaw 2026.9.8Anthropic turns finish after background Bash
Later messages are no longer silently skipped.
When a Bash command moved into the background, an Anthropic turn could stay open until the watchdog killed it. Those turns now finish normally, and your later messages go through.
Codex Computer Use and session discovery
OpenClaw 2026.9.8Codex fixes for Computer Use and big fleets
Codex Computer Use now checks native app control without going through browser authentication. And on large agent fleets, Codex session discovery no longer runs the Gateway out of memory.
Windows cron and sessions
OpenClaw 2026.9.8Windows cron jobs run again
Cron setup and session admission are restored.
On Windows, cron agent turns and session admission could fail before they started, with a data clone error. Both work again, and the fix needs no configuration changes.
Sandbox skills on read-only installs
OpenClaw 2026.9.8Sandboxed sessions survive a skills refresh on read-only installs
Every turn used to fail with a permission error.
If your Gateway runs from a read-only install, a skills refresh could make every sandboxed turn fail with a permission error. Those sessions now keep working when skills change or the Gateway restarts.
Telegram preview edits
OpenClaw 2026.9.8Telegram previews respect the current writer
Writer authority is rechecked before each queued edit.
In Telegram, a queued preview edit could still be sent after its writer lost authority, landing over the new writer's message. OpenClaw now rechecks writer authority before each queued edit.
04: Before you upgrade
OpenClaw 2026.9.8Before you upgrade.
Android stays at 2026.8.2
OpenClaw 2026.9.8The Android app stays at 2026.8.2
Its APK was skipped for this release.
If you run OpenClaw on Android, the APK was skipped for this release, so the Android app stays at 2026.8.2.
Telegram checks waived
OpenClaw 2026.9.8Telegram integration checks were waived for this release
Telegram users should know that the release owner waived the Telegram integration checks, so they didn't run on this build. The full list of fixes is in the 2026.9.8 changelog.
