OpenClaw
OpenClaw withdraws its 2026.9.6 Mac update after launch crashes
OpenClaw warns Mac users not to install 2026.9.6 and says it has withdrawn the app from Sparkle while preparing a hotfix. Its npm/Gateway release is unaffected. A report from two Macs makes the immediate choice a platform-specific hold, not a blanket rollback.
OpenClaw has put a stop sign in front of its new Mac application. The warning on the 2026.9.6 release says the app can crash on every launch after an in-app update, has been removed from the Sparkle update feed, and should not be installed yet. It directs affected users to the 2026.9.5 Mac build while a 2026.9.7 hotfix is being prepared. That is the project's recovery guidance, not a hotfix availability claim.
The distinction matters because the same release number also labels the npm/Gateway package. The project explicitly excludes that package from this warning. Treating every component with the version string as equally affected would turn a useful notice into unnecessary operational churn.
The facts
- The 2026.9.6 release page carries an explicit warning against updating the macOS app. - The notice says the Mac build was withdrawn from Sparkle and a 2026.9.7 Mac hotfix is in progress. - The same notice says the npm/Gateway package 2026.9.6 is unaffected. - Issue 156861 reports failed relaunches on a MacBook and a Mac Studio after Settings → Update. - Three supplied reports identify build 2609000690 and macOS 27.0; the starting app version is not established precisely. - The issue places CookieSyncManager in the crashing stack but explicitly does not establish the disabled Chrome permission as the cause.
Why it matters
An updater is part of the product's reliability contract: users need a working application after accepting the invitation to update. This community report is especially consequential because the affected installations cannot reopen the app to reach its normal controls. The operator risk is loss of access, not a missing convenience feature. Maintenance policy should therefore separate the Mac application from the Gateway instead of treating one shared number as a single deployment decision.
The evidence also sets limits on diagnosis. The reporter's prior installation state is not fully established, and a permission toggle is not proof of causation. Broader consent to Chrome access would be a policy change, not an evidence-backed repair. Keeping that boundary explicit avoids turning recovery friction into an unnecessary expansion of access. The next meaningful signal is a verified relaunch on the affected path, not another long list of improvements.
Current
Checked September 24, 2026. The inspected release baseline is npm latest 2026.9.6; extended-stable 2026.7.35; the Mac app warning is a separate component-specific notice. The primary source is published release warning. Package availability and development-source state are separate: a tag does not establish that an open proposal is usable, and a merge does not establish that every installation has received it.
Evidence
Primary: openclaw/openclaw — v2026.9.6 release notice (https://github.com/openclaw/openclaw/releases/tag/v2026.9.6). Supporting context: openclaw/openclaw issue #156861 (https://github.com/openclaw/openclaw/issues/156861); openclaw/openclaw — v2026.9.5 release notice (https://github.com/openclaw/openclaw/releases/tag/v2026.9.5). Source pages and available diffs were inspected; test and live-account results remain attributed to their authors, not independently repeated measurements.
Operator take
Hold the Mac app update and track the release warning for the hotfix. If already affected, use the project's linked previous Mac release as the documented recovery route. Keep the npm/Gateway deployment decision separate. Before considering the incident resolved, look for evidence that the affected update path and subsequent launches work, not merely that a replacement download exists. No machine was upgraded or repaired as part of this report.
Caveat
This is a project warning corroborated by a user report, not an independent reproduction or an estimate of affected users. The exact pre-update builds and a clean-install reproduction remain uncertain. A disabled Chrome access toggle is observed context, not a proven root cause; do not grant broader permissions on that basis.
This is a project warning corroborated by a user report, not an independent reproduction or an estimate of affected users. The exact pre-update builds and a clean-install reproduction remain uncertain. A disabled Chrome access toggle is observed context, not a proven root cause; do not grant broader permissions on that basis.