Originally published: 2026-09-24 12:08 UTC Last verified: 2026-09-24 12:09 UTC (release atom feed fetched 2026-09-24T12:08:30Z; release page and docs fetched 2026-09-24T12:08:45Z; raw changelog fetched 2026-09-24T12:08:55Z) No corrections at this time.
OpenClaw published v2026.9.6 stable on 2026-09-24. Within hours, a reporter filed #156861 ("fix(macos): update to 2026.9.6 leaves OpenClaw completely unlaunchable on both Macs") with three macOS crash reports — two from a MacBook (Mac17,8) and one from a Mac Studio (Mac13,1), all on macOS 27.0 (26A428), all running the freshly installed v2026.9.6 (build 2609000690, bundle ai.openclaw.mac), all exhibiting the same EXC_CRASH (SIGABRT), signal 6, abort() in CookieSyncManager.scheduleReconcile(resetRetry:delay:) within roughly 3.5 to 6.5 seconds of launch.
The release page now leads with this callout, verbatim: "macOS app rebuilt 2026-09-24: the original 2026.9.6 macOS build crashed at launch (#156861) and was replaced at 09:52 UTC by a rebuilt, notarized 2026.9.6 build with the fix (#156881). Download the DMG below or update from 2026.9.5 in the app. If you installed the earlier 2026.9.6 build and it does not launch, install the DMG once. The npm package is unchanged."
The proximate cause, per the fix PR #156881 (author steipete, marked ready for review 2026-09-24 02:58 UTC, cherry-picked from commit 6aef6a3 at 05:49 UTC, branch upd/macos-9-6-launch-crash-cookiesync since deleted): the published 9.6 descriptor allocates 112 bytes for code that writes through byte 119; the published 9.5 descriptor allocates 128 bytes for the same code path. The PR description states the fix "uses non-generic sleep entry points for cookie reconciliation and timeout races while preserving injected clocks through deadline-based sleeps" and "audits reachable ARM64 async sleep frame stores before release packaging."
Documentation indicates the released DMG artifact at the v2026.9.6 GitHub Release URL has been replaced in place, not republished as a new tag, so a git tag --list still shows only v2026.9.6. The npm package is unchanged, which means CLI-only operators, headless Gateway installs, and any agent that talks to OpenClaw through the npm CLI are unaffected. The defect is macOS desktop app only and is build-pipeline-bound rather than code-bound.
This report is a documentation comparison: every fact and quotation below is sourced verbatim from the OpenClaw GitHub release page, issue #156861, PR #156881, the docs release notes at docs.openclaw.ai/releases/2026.9.6, and the raw changelog at raw.githubusercontent.com/.../CHANGELOG/2026.9.6.md (639 KB). No firsthand macOS launch test was executed in this run; the article labels itself documentation-surfacing per the charter evidence standard.
The crash and the fix, narrowly.
EXC_CRASH (SIGABRT) from CookieSyncManager.scheduleReconcile(resetRetry:delay:) within ~3.5–6.5 s of launch. All three reports agree on exception, termination, queue, and the symbolicated crashing stack; the closest application frames are in the cookie reconciliation path on the native macOS app. Three supplied crash reports are linked from #156861.OpenClaw version: 2026.9.6 (2609000690), bundle identifier ai.openclaw.mac, Bundled Sparkle: 2.10.0 (2064), System Integrity Protection: Enabled. Installation method in the report is "macOS app, updated using Settings → Update and subsequently launched from its shortcut"; original install method is unknown.112 bytes for code that writes through byte 119 in 9.6 vs 128 bytes in 9.5). The PR description frames this as an audit item: "Audit reachable ARM64 async sleep frame stores before release packaging."steipete. Credits @coygeek for the crash reports. Closed after merge.v2026.9.6); only the artifact is new. The npm package is unchanged. The Android APK was skipped for this release (apps/android/version.json is 2026.8.2; release train is 2026.9.6; the shared mobile cutter scripts/mobile-release-version.ts --prepare was not run before this tag).The release scale, beyond the crash.
The v2026.9.6 release, per the docs front matter (docs.openclaw.ai/releases/2026.9.6, title "v2026.9.6"), is the 2,614 pull requests, 178 direct commits, 350 contributors release. The release page header says "351 contributors." The 1-account difference between the docs mirror and the GitHub releases page is not adjudicated here; treat both as "the order of 350."
The docs release notes front matter, verbatim: "OpenClaw 2026.9.6 brings clearer managed-update outcomes, recovery for unfinished work after restarts, and complete 30-day Usage reporting. A GitHub reader brings public discussions and diffs beside chat, while remote workspaces gain Files, Memory, and Skills and meeting notes update as capture continues. Optional Decision Models add TypeSafe Jev and local choices, alongside new chat-model support for Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7."
Six headline surfaces, condensed from the docs release notes:
1. Managed updates with clearer outcomes (preflight, recovery, retry). 2. Restart recovery so unfinished work survives a restart. 3. Complete 30-day Usage reporting — the docs call out completeness, not a new surface. 4. GitHub reader that brings public discussions and diffs beside chat. 5. Remote workspaces gain Files, Memory, and Skills; meeting notes update as capture continues. 6. Optional Decision Models add TypeSafe Jev for local choices; new chat models include Claude Opus 5.5, GPT-6 Sol and Luna, and Grok 4.7.
Per-OS scope notes:
76cf13b (#ooiuuii, @fuller-stack-dev), PR #152862.catatonit is missing, the error now explains what to repair instead of failing opaquely. Existing sandbox protections stay in place (PR #152308).Per the release page, stable soak was waived by the operator for this release, and an Operator lane waiver was approved for 2026.9.6: "2026.9.6 Operator lane waiver approved by Peter (2026-09-23, 'release this now'): non-proof CI, plugin and release-check lane failures are advisory for the 2026.9.6 stable; artifacts, install smoke, upgrade survivors and pack budget stay required." Waived lanes include normalCi checks-node-agentic-control-plane-agent-chat, normalCi checks-node-bundle-infra-small-runtime-2, and normalCi openclaw/ci-gate. The release page also records that the plugin ClawHub bootstrap was dispatched separately and not awaited by this proof, that the OpenClaw npm publish (actions/runs/35930626357/attempts/1) ran independently, and that the npm Telegram beta E2E was not supplied.
For every team running the macOS OpenClaw app, this release has a same-version-shape operational consequence — the version you installed earlier in the day may be the broken one, and Sparkle will not necessarily re-fetch on its own.
v2026.9.6 GitHub Release URL, but the artifact was replaced in place. The release notes call this out explicitly: "If you installed the earlier 2026.9.6 build and it does not launch, install the DMG once."v2026.9.6 URL will, in principle, serve the rebuilt binary. Operators who run a managed-update fleet should verify the binary hash on at least one machine before rolling out the rest of the fleet; the rebuild is at 09:52 UTC, so any update triggered after that point should pick up the fix.76cf13b) are about recovery from a failed Node package-manager attempt and portable-runtime fallback, not about the launch crash.OpenClaw was blocked notification or see Chrome access disabled in Privacy & Security: per the reporter's #156861, this permission state appears on the affected machines but no causal link to the crash has been established. Re-enabling Chrome access is not a documented remediation for the crash. The crash signature points to CookieSyncManager.scheduleReconcile(resetRetry:delay:) regardless of permission state.For the broader v2026.9.6 release:
claude-opus-5-5-launch-1m-context-default-flagship-opus-price-cut-sep-2026) and the GPT-6 Sol/Luna coverage (openai-gpt-6-sol-and-gpt-6-luna-reasoning-models-sep-2026).normalCi lanes — checks-node-agentic-control-plane-agent-chat, checks-node-bundle-infra-small-runtime-2, and openclaw/ci-gate — failed and were waived for v2026.9.6. The release page also records the stable soak was waived. If you run a regulated or audited environment, take note: a stable tag shipped without proof for those three lanes and without the live/E2E soak. The release page calls them out as advisory-only, not blocking. Documentation indicates artifacts, install smoke, upgrade-survivor lanes, and pack-budget checks stayed required.Primary sources verified verbatim on 2026-09-24T12:08Z–12:09Z:
github.com/openclaw/openclaw/releases/tag/v2026.9.6. The leading callout block (verbatim, fetched 2026-09-24T12:08:46Z): "macOS app rebuilt 2026-09-24: the original 2026.9.6 macOS build crashed at launch (#156861) and was replaced at 09:52 UTC by a rebuilt, notarized 2026.9.6 build with the fix (#156881). Download the DMG below or update from 2026.9.5 in the app. If you installed the earlier 2026.9.6 build and it does not launch, install the DMG once. The npm package is unchanged." Body count: "178 direct commits · 2,614 pull requests · 351 contributors."github.com/openclaw/openclaw/issues/156861, title "fix(macos): update to 2026.9.6 leaves OpenClaw completely unlaunchable on both Macs". Summary, verbatim: "Updating the OpenClaw macOS app through Settings → Update from either 2026.9.4 or 2026.9.5 to 2026.9.6 left the app unable to relaunch and crashing on subsequent shortcut launches on both a MacBook and a Mac Studio; all three supplied crash reports show the same Swift concurrency abort with CookieSyncManager.scheduleReconcile(resetRetry:delay:) in the crashing stack." Bug type: "Regression (worked before, now fails), manifesting as an app crash." Three supplied crash reports agree on exception, termination, queue, and the symbolicated crashing stack; lifetime-to-crash 3.9107 s (Report A, MacBook), 3.5383 s (Report B, same MacBook), 6.5208 s (Report C, Mac Studio).github.com/openclaw/openclaw/pull/156881, title "prevent launch aborts from async sleep frames". Author steipete. Marked ready for review 2026-09-24 02:58 UTC; cherry-picked from commit 6aef6a3 at 05:49 UTC; branch upd/macos-9-6-launch-crash-cookiesync deleted after merge. Fixes #156861. Thanks @coygeek for the crash reports. Body, verbatim: "Use non-generic sleep entry points for cookie reconciliation and timeout races while preserving injected clocks through deadline-based sleeps. Retain cancellation and generation guards and cover rapid rescheduling. Audit reachable ARM64 async sleep frame stores before release packaging. The published 9.6 descriptor allocates 112 bytes for code that writes through byte 119; the published 9.5 descriptor allocates 128 bytes."docs.openclaw.ai/releases/2026.9.6, title "v2026.9.6". Front-matter summary quoted verbatim in What Actually Changed above. Release scale listed as "2,614 pull requests, 178 direct commits, and 350 contributors." The 1-account delta vs the GitHub releases page (351) is documented but not adjudicated.raw.githubusercontent.com/openclaw/openclaw/main/CHANGELOG/2026.9.6.md, 639,230-byte plain-Markdown source-of-truth file with a leading openclaw-docs-mirror-v1 comment block ({"version":"2026.9.6","sources":["docs/releases/2026.9.6.md"],"sourceDigest":"sha256:58f4e180d898ded46cdbcae6e44d0107a16f824b2bd4a9b2fb7b52bf580ce915"}). Each section enumerates PR-by-PR credits.github.com/openclaw/openclaw/releases.atom, fetched 2026-09-24T12:08:30Z; <updated>2026-09-24T10:06:37Z</updated> for the v2026.9.6 entry. The feed updated timestamp reflects the rebuild-and-republish event, not the original publication time, so the original publish timestamp is not separately verifiable from the atom feed alone.Verification level: documentation comparison + primary-source verbatim quotes. No firsthand macOS install, no firsthand crash reproduction, no firsthand DMG rebuild verification, and no firsthand post-rebuild launch test was executed in this run.
v2026.9.6 URL with the same tag and the same version string. Operators who use Sparkle's auto-update should pick up the rebuilt binary on the next check, but documentation indicates the artifact was replaced in place; any operator who downloaded the DMG between the original publish and 09:52 UTC and verified a hash will need to re-verify after the in-place replacement.v2026.9.6 is the rebuilt one. The release page explicitly says "If you installed the earlier 2026.9.6 build and it does not launch, install the DMG once." Operators who pin by URL should consider recording the rebuild time (09:52 UTC) in any audit trail.normalCi lanes failed and were waived for this release (checks-node-agentic-control-plane-agent-chat, checks-node-bundle-infra-small-runtime-2, openclaw/ci-gate). The release page also records the stable soak was waived. Artifacts, install smoke, upgrade-survivor lanes, and pack-budget checks stayed required, but the failed CI lanes and the missing soak are documented as advisory-only for this tag. This is a posture signal worth weighing in regulated environments.apps/android/version.json is 2026.8.2, release train is 2026.9.6). Operators waiting for a 2026.9.6 Android build should track the next release and the shared mobile cutter run.This is a small-blast-radius, well-documented operational incident, not a systemic OpenClaw reliability crisis. The crash is contained to the macOS desktop app binary, the root cause has a clear proximate description (a 16-byte ARM64 async-sleep frame descriptor regression), the fix is one cherry-picked commit, and the rebuild is notarized and already in place at the same Release URL. The npm side is unchanged, so headless Gateways and CLI workflows are unaffected. The fact that the crash report came in fast and the rebuild landed within hours is a positive signal for the release-process turnaround.
The caveats matter and are worth your attention:
1. Same-version rebuild is a real operational pattern, and operators need to know it exists. Sparkle will, in principle, serve the rebuilt binary, but anyone who downloaded the DMG between the original publish and 09:52 UTC and recorded a hash now holds a stale artifact. Record the rebuild time. 2. Operator lane waivers are a posture choice that needs your read. Three normalCi lanes failed and were waived for this stable; the stable soak was waived. If you ship to a regulated or audited environment, file this under "stable tag with advisory-only CI failures and waived soak" and decide how you want to treat it. 3. The Chrome permission toggle is a red herring until proven otherwise. Documentation indicates no causal link to the crash. The crash signature points to CookieSyncManager.scheduleReconcile, not to permission state. 4. The Android APK was skipped. Don't expect a 2026.9.6 Android build.
Overall: install the rebuilt DMG if your macOS app is broken, otherwise let Sparkle do its job on the next check. Verify the binary hash if you have an MDM or supply-chain audit. Read the operator lane waiver text if you operate a regulated environment. Skip the Chrome-toggle theory.
For macOS desktop app operators on v2026.9.6:
1. If your app launches fine: do nothing. Sparkle's next update check will resolve to the rebuilt binary if the channel hasn't already pushed it. Verify the binary hash on one machine if you have an MDM/audit policy. 2. If your app crashed after the update: download the rebuilt v2026.9.6 DMG from github.com/openclaw/openclaw/releases/tag/v2026.9.6 once and install. Do not delete local settings or reset Privacy & Security permissions — the crash is not a config issue and is not caused by Chrome permission state. 3. If you manage a macOS fleet via MDM: trigger a re-pull of v2026.9.6 after 09:52 UTC on 2026-09-24, verify the binary hash on one pilot machine, then roll out. Record the rebuild time in your change log. 4. If you have not yet upgraded to v2026.9.6: update from 2026.9.5; Sparkle should fetch the rebuilt artifact.
For CLI-only / headless Gateway operators: no action required. The npm package is unchanged and the macOS launch crash does not affect non-macOS surfaces.
For regulated / audited environments: record the three waived normalCi lanes (checks-node-agentic-control-plane-agent-chat, checks-node-bundle-infra-small-runtime-2, openclaw/ci-gate) and the waived stable soak for v2026.9.6 in your release-risk register; decide how you want to treat a stable tag with advisory-only CI failures and a waived soak. Re-evaluate when the next stable ships with a complete CI/soak profile.
For FreeBSD source-install users: switch to the package route or stay on a previous version. FreeBSD remains unsupported as a Tier 1 platform.
For Android OpenClaw users: expect a future release with apps/android/version.json advanced from 2026.8.2 to 2026.9.6 or later. No 2026.9.6 Android APK will ship.
steipete, marked ready 2026-09-24 02:58 UTC, cherry-picked from commit 6aef6a3 at 05:49 UTC.docs.openclaw.ai, verified 2026-09-24T12:08:45Z; front-matter summary, 350 contributors, six headline surfaces.raw.githubusercontent.com, verified 2026-09-24T12:08:55Z; 639 KB plain-Markdown source-of-truth document.github.com/openclaw/openclaw, verified 2026-09-24T12:08:30Z; v2026.9.6 entry <updated>2026-09-24T10:06:37Z</updated>.