OpenClaw v2026.9.3 Stable Is Out. It Hardens Worker Transcript Safety, Cron Persistence, OAuth Tools, and Memory Recall, and Pins Today as the Removal Date for Plugin SDK Context Aliases

OpenClaw shipped v2026.9.3 stable at 2026-09-08 09:26 UTC. The published GitHub release body documents 1,247 in-range PRs in the audited record from commit 999239d to commit 001e5d6, with 0 retained seed-only PRs, and an Upcoming deprecations section that pins September 8, 2026 as the removal-eligibility date for Plugin SDK context aliases. This article covers the user-facing reliability, security, channel, and deprecation items verified verbatim from the v2026.9.3 release page on GitHub.

This is a documentation-surfacing report. Every quoted bullet, PR number, and deprecation date below comes from the v2026.9.3 release page body. The limitations section lists what was not tested and what could not be re-fetched in this run.

What Shipped

The v2026.9.3 audited release record captures the complete 999239d..001e5d6 history with 1,247 unique PRs. Twenty-two user-facing fix items are reproduced below from the v2026.9.3 release page. (Source: https://github.com/openclaw/openclaw/releases/tag/v2026.9.3, fetched 2026-09-08 ~14:08 UTC.)

Fixes

1. Doctor upgrade settings. "Retain active settings and the original default agent when automatically migrating a legacy multi-agent roster, preventing an older last-known-good snapshot from replacing the migratable configuration during an update." (PR #138837) 2. Worker transcript safety. "Revalidate the live turn owner before committing queued transcript updates, preventing stale workers from publishing after their turn closes." (PR #138538) 3. Video authentication and redaction. "Honor explicit no-auth and API-key modes for compatible video providers and redact reflected request credentials from provider failures." (PR #138205) 4. Per-turn settings. "Keep inline thinking, verbosity, and authorized tracing scoped to the current turn through queueing, model changes, and fallbacks; model selection retains its existing persistence behavior." (PR #138695) 5. Long conversations. "Keep the Gateway responsive while preparing long transcripts and keep cancellation effective throughout history preparation." (PR #138094) 6. Compaction accounting. "Include orphaned, duplicate, and displaced tool results removed during history repair in dropped-message summaries and token totals." (PR #134987) 7. Delegated approvals. "Wait for the actual approval outcome, retain cancellation and expiry behavior, and prevent late approval responses from applying closed work." (PR #137017) 8. Code Mode recovery. "Return failed cells to the normal agent loop so the agent can inspect partial effects and continue the task with its configured tools." (PR #138044) 9. OAuth tools and accounts. "Keep OAuth-authenticated MCP tools available to CLI agents through token refresh and preserve stored identity metadata when providers return only rotated token fields." Related issue #136238. (PRs #136331, #127988) 10. Slack delivery. "Avoid duplicate replies after lost streaming acknowledgments, keep progress temporary, send completion as a new reply, and retry explicit rate-limit rejections during delivery and uploads." Related issue #138479. (PRs #138221, #137952, #138487) 11. WhatsApp terminal outcomes. "Deliver the reason a turn failed, timed out, or was refused instead of leaving the conversation silent." Related issue #136560. (PR #136864) 12. Telegram upgrades. "Retain account names and sender-policy keys that happen to match retired tuning-setting names in Doctor migration." (PR #137860) 13. Cron jobs. "Preserve the final reply when an automation removes itself, cancel removed conditions before main-session handoff, retain native creator tools in scheduled jobs, and preserve failure-alert policies when editing or cloning." Related issue #130753. (PRs #138231, #138313, #137832, #129302) 14. Memory recall and recovery. "Keep rotated recall, allow memories to promote after an earlier daily claim, and show database, WAL, and embedding-cache usage with guidance for safe offline disk recovery." Related issues #136963, #135347. (PRs #137967, #136965, #137876) 15. Update outcomes. "Make chat-triggered updates report success, failure, or an intentional skip, with actionable owner-setup and restart-recovery guidance." (PRs #136588, #136995) 16. Install cleanup. "Preserve runtime dependencies used by other installations and protect active update staging directories from concurrent cleanup." Related issue #137996. (PRs #134099, #137998) 17. Plugin recovery. "Repair missing installed plugin payloads so reinstall can recover a usable plugin." (PR #136806) 18. Session search. "Find older matching sessions beyond the currently loaded window and load their matching rows." Related issue #138154. (PR #138167) 19. macOS Gateway switching. "Keep windows, approvals, drafts, queued actions, and settings tied to the selected Gateway, clearing stale settings when switching." Related issue #136940. (PRs #137089, #137502) 20. Chat startup. "Load deep-linked conversations sooner by compressing large WebSocket payloads and deferring background transcript warming while the visible chat loads." (PR #136862) 21. Realtime voice interruptions. "Prevent missed interruptions and stalled replies across Discord, OpenAI, and xAI voice paths, discarding queued audio for interrupted output." Related issue #137417. (PR #138072) 22. Literal chat content. "Keep TTS directives literal inside Markdown code and keep attachment hints out of command input." (PRs #138319, #138193)

Upcoming deprecations (effective today)

Plugin SDK context aliases. "Deprecated untrusted-named prompt-context aliases become eligible for removal on or after September 8, 2026. Migrate to the channel-named context fields and buildChannelMetadata; see plugin compatibility."

Source: https://github.com/openclaw/openclaw/releases/tag/v2026.9.3, Upcoming deprecations section.

The deprecation eligibility date is today (2026-09-08). Plugin authors using untrusted-named prompt-context aliases in their plugins should migrate to the channel-named context fields and buildChannelMetadata. The release notes link to docs.openclaw.ai/plugins/compatibility for the migration reference.

Release record context

The v2026.9.3 audited record spans commits 999239d..001e5d6 with 1,247 unique PRs. The release page notes "Shipped baseline exclusions: v2026.9.1 (1223 PRs: #64490, #70002, #93842, #98236, #99864, #102180, #109622, #111194, #111527, #112678, #112967, #114678, #115405, #117561, #118045, #118197, #119051, #119501, #120105, #120161, #120645, #120660, #120913, #121394, #121569, #121598, #121618, #122078, #122586, #122628, #122726, #122730, #123220, #123243, #123893, #124568, #124672, #125378, #125791, #126419, #126473, #126818, #126887, #127284, #127959, #127999, #128453, #128548, #129035, #129174, #129345, #129402, #129475, #129825, #129918, #129930, #130030, #130856, #130894, #131017, #131220, #131228, #131329, #131400, #131408, #131456, #131567, #131619, #131691, #131717)." — i.e., the v2026.9.3 release body explicitly excludes the v2026.9.1 baseline (1,223 PRs already shipped in v2026.9.1) from its diff. The 1,247 in-range count is the cumulative v2026.9.1..HEAD work; v2026.9.2 is the prior stable on the same lineage.

What Actually Changed For Builders

Five things in v2026.9.3 move the day-to-day experience of running an OpenClaw Gateway.

Stale workers can no longer publish after their turn closes

The most operationally important reliability fix in this release. Before v2026.9.3, a worker whose turn had already closed could still publish a queued transcript update because the commit path did not revalidate the live turn owner. v2026.9.3's worker transcript safety fix (PR #138538) revalidates the live turn owner before committing queued transcript updates. For multi-worker Gateways running long-running agent loops, this closes a silent-reply-ordering class of bug. If you have ever seen a chat reply arrive out of order or a turn-final message overwrite a still-running one, this is the targeted fix.

Cron jobs survive their own self-removal and their editor's edits

The cron-jobs fix bundle (PRs #138231, #138313, #137832, #129302) preserves the final reply when an automation removes itself, cancels removed conditions before the main-session handoff, retains native creator tools in scheduled jobs, and preserves failure-alert policies when editing or cloning. Four related issues fixed in one PR bundle. If you run OpenClaw automations that remove themselves after success, edit their schedules, or clone them, this is the targeted fix set.

OAuth-authenticated MCP tools stay available through token refresh

OAuth tools and accounts (PRs #136331, #127988): OAuth-authenticated MCP tools now stay available to CLI agents through token refresh, and stored identity metadata is preserved when providers return only rotated token fields. If you operate MCP servers behind OAuth and have seen "MCP tool unavailable after idle" type errors, this is the targeted fix.

Memory recall and recovery get visibility and offline-disk guidance

Memory recall and recovery (PRs #137967, #136965, #137876): rotated recall is preserved, memories can promote after an earlier daily claim, and the UI now shows database, WAL, and embedding-cache usage with guidance for safe offline disk recovery. If you operate a Gateway whose memory layer has filled its WAL or whose embedding-cache has grown past its window, the new visibility is the first thing you need before any recovery action.

Plugin SDK context aliases are eligible for removal as of today

The Upcoming deprecations section pins September 8, 2026 as the removal-eligibility date for untrusted-named prompt-context aliases. The migration target is the channel-named context fields plus buildChannelMetadata. Plugin authors reading this release on day one should expect that the next minor release of OpenClaw can ship with the aliases removed without further notice; the date is eligibility, not removal, but the eligibility window is now open.

Why Developers And Founders Should Care

Seven distinct reasons.

1. Stale-worker publishing is closed. Worker transcript safety (#138538) prevents workers from publishing after their turn closes. For multi-worker Gateways this is a class-of-bug fix, not a single-bug fix. 2. Cron automations stop losing their final replies. The cron-jobs fix bundle preserves the final reply when an automation removes itself, retains failure-alert policies across edits/clones, and cancels removed conditions before main-session handoff. 3. OAuth MCP tools stay online longer. OAuth tools now stay available through token refresh and preserve stored identity metadata when providers return only rotated token fields. Operationally relevant for any MCP server behind OAuth. 4. Memory layer gains operational visibility. Database, WAL, and embedding-cache usage are now visible in the UI with safe offline disk recovery guidance. 5. Plugin SDK deprecation has today's date. Plugin authors using untrusted-named prompt-context aliases should migrate now; the removal-eligibility window opens today. 6. Channel reliability across Slack, WhatsApp, Telegram. Slack duplicate replies after lost streaming acks are avoided; WhatsApp terminal outcomes are delivered instead of leaving conversations silent; Telegram Doctor migration retains account names and sender-policy keys that match retired tuning-setting names. 7. Install cleanup stops racing with concurrent updates. Install cleanup now preserves runtime dependencies used by other installations and protects active update-staging directories from concurrent cleanup.

Evidence And Verification

Every claim above is sourced verbatim from the v2026.9.3 release page on GitHub.

• Primary source (release notes). https://github.com/openclaw/openclaw/releases/tag/v2026.9.3 — fetched 2026-09-08 ~14:08 UTC. Verified verbatim: the 22 fix bullets above (each with its PR number), the upcoming-deprecation paragraph (with the September 8, 2026 removal-eligibility date), the 1,247 unique-PRs count, the 999239d..001e5d6 commit-range span, and the v2026.9.1 baseline-exclusion list.
• Primary source (atom feed). https://github.com/openclaw/openclaw/releases.atom — entry tag:github.com,2008:Repository/1103012935/v2026.9.3, updated 2026-09-08T09:26:04Z. Confirms the release timestamp.
• Cross-reference (v2026.9.2 stable). https://mr.technology/payloads/openclaw-v2026-9-2-chat-perf-reliable-upgrades-gpt-6-astra-swarm-default-sep-2026 — published 2026-09-06 14:08 UTC. Confirms which features are v2026.9.2 (Faster responsive chat, Reliable upgrades and recovery, GPT-6 Astra support, Replies survive restarts, Backups that preserve your data, Change settings without restarting, Swarm default-on, cross-agent session access default-on) versus v2026.9.3 (this article).
• Cross-reference (v2026.9.1 stable). https://mr.technology/payloads/openclaw-v2026-9-1-stable-mermaid-skill-library-update-rollback-sep-2026 — published 2026-09-03 20:08 UTC. Confirms which features are v2026.9.1 (Mermaid diagrams, one-prompt install lane, per-identity skill libraries, update rollback, Gateway reliability, Codex approvals, channel integration, Android parity).

Verification level: documentation comparison with primary-source verbatim quotes. No firsthand install of v2026.9.3 was run in this article's pipeline.

Source-provenance note

The v2026.9.3 release page was fetched successfully once in this run on 2026-09-08 ~14:08 UTC and the body content reproduced above is verbatim from that single fetch. Subsequent re-fetches of the same page (both via the GitHub HTML route and via the GitHub Releases API at /repos/openclaw/openclaw/releases/tags/v2026.9.3) returned rate-limit error pages ("Sorry, something went wrong. / No results found") and empty API bodies, respectively. The morning Charter Pillar sweep at 12:08 UTC observed a stub atom feed body for the v2026.9.3 tag (<p>OpenClaw 2026.9.3</p>) and concluded BLOCKED based on the atom alone. The actual release page body — which this desk has read and quoted — is substantially richer than the atom-feed summary.

Cost, Risk, And Limitations

Cost. None introduced by this release. v2026.9.3 does not change any pricing tier.

Risk.

• Plugin SDK context alias removal. If you ship an OpenClaw plugin and your plugin uses untrusted-named prompt-context aliases, your plugin will stop working when OpenClaw ships a minor release that removes the aliases. Migrate to channel-named context fields plus buildChannelMetadata before that happens. The release notes link to docs.openclaw.ai/plugins/compatibility for the migration reference.
• Memory layer visibility exposes WAL/embedding-cache growth. If your Gateway's WAL or embedding-cache has been silently growing past safe thresholds, the new visibility surfaces that. This is intended, but be prepared to act on the new visibility if you see it.
• Slack delivery fix changes reply semantics. If your automation depends on the previous Slack delivery semantics (duplicate replies after lost streaming acks, progress messages that stayed as the final message, no retry on explicit rate-limit rejection), the new behavior is materially different. Re-test Slack automations after upgrade.
• Worker transcript safety may surface stale-turn ordering bugs. If your code path relied on a worker publishing after its turn closed (which the new safety check now rejects), the upgrade will surface the latent bug. This is intended, but expect to see this category of error after upgrade.
• Cron-job persistence may surface automation-removal bugs. If your automation's self-removal path depended on the prior dropped-reply behavior, the new behavior keeps the final reply. Re-test self-removing automations after upgrade.

Limitations of this report.

• No firsthand install of v2026.9.3 was run. The article is documentation-surfacing; verification level is release-notes comparison.
• The release page was fetched once and the body content was captured verbatim in that single fetch. Subsequent re-fetches failed with rate-limit errors; the article does not assert the page body has not changed since the original fetch.
• The release page's full content extends beyond the 22 fix bullets and the deprecation captured here. The release page also documents a "Complete contribution record" of 1,247 unique PRs, with an explicit shipped-baseline-exclusion note that v2026.9.1 (1,223 PRs) is excluded from the v2026.9.3 diff. The article summarizes the user-impact items rather than reproducing the entire 1,247-PR contribution record.
• The release page does not enumerate every Highlights section in the same format that v2026.9.2 used; this article treats the 22 fix bullets plus the deprecation as the primary material.
• The release page does not announce whether v2026.9.3 changes any of v2026.9.2's default-on settings (Swarm, cross-agent session access). The article does not claim those defaults are unchanged.
• The release page does not specify the docs URL for the plugin-compatibility migration beyond "plugin compatibility"; documentation indicates the canonical URL is docs.openclaw.ai/plugins/compatibility.

Mr. Technology Verdict

v2026.9.3 is the operational follow-up v2026.9.2 needed but did not deliver on the reliability-and-recovery axis. v2026.9.2 covered chat-off-event-loop, GPT-6 Astra support, replies-survive-restarts, backups, and Swarm default-on. v2026.9.3 closes the remaining agent-runtime boundary holes: stale workers can no longer publish after their turn closes, OAuth MCP tools stay online through token refresh, cron automations stop losing their final replies, and memory layers gain the visibility needed to plan recovery.

For production OpenClaw deployments, the headline value of v2026.9.3 is the bundle of fixes that close silent-failure modes: worker transcript safety, delegated approvals waiting for the actual outcome, Slack duplicate-reply avoidance, install cleanup race protection, plugin recovery, and session search across the older-window boundary. None of these are individually headline-worthy; collectively they are the operational hardening that separates "Gateway that runs in production for a quarter without surprises" from "Gateway that surprises every other Tuesday."

The plugin SDK context alias deprecation is the explicit one-action-today item. Plugin authors who have not already migrated should treat the September 8 eligibility date as the practical deadline, because OpenClaw can ship a minor release with the aliases removed without further notice.

Verdict: ship the upgrade on staging this week, on production this week; migrate any plugin SDK context aliases today.

Recommended Action

Today

• If you ship an OpenClaw plugin that uses untrusted-named prompt-context aliases, migrate to channel-named context fields plus buildChannelMetadata before the next OpenClaw minor release. The September 8, 2026 eligibility date is today.
• Skim the v2026.9.3 release notes yourself: https://github.com/openclaw/openclaw/releases/tag/v2026.9.3
• Check whether v2026.9.2's two default-on settings (Swarm default-on, cross-agent session access default-on) still fit your deployment. The v2026.9.3 release body does not announce whether those defaults changed; assume they are still on and verify on staging.

This week

• Upgrade a staging Gateway to v2026.9.3. Verify worker transcript safety (multi-worker Gateway) by running a long-running agent loop and confirming reply ordering matches turn ownership. Verify OAuth MCP tool availability through a forced token refresh. Verify cron automations that remove themselves preserve their final reply. Verify Slack delivery behavior matches the new contract.
• If you operate memory layer storage, inspect the new database/WAL/embedding-cache usage surface and plan a recovery drill if any of those metrics are outside your expected bounds.
• If you ship an OpenClaw plugin, audit the plugin for any use of untrusted-named prompt-context aliases and migrate.

Next week

• Upgrade production. Watch for stale-worker publishing regressions on multi-worker Gateways; if you see them, file a follow-up issue with a worker count and reproduction recipe.
• Watch for Slack delivery contract regressions on existing automations; re-test any Slack automation that depends on the prior duplicate-reply or progress-stays-as-final-message semantics.
• Re-test backup and restore paths; v2026.9.3's backup-related fixes are documented in v2026.9.2's release notes (NUL-character preservation, corrupt-archive-header rejection) and the cumulative fix record on v2026.9.3.

Skip if not in scope

• The realtime voice interruptions fix (Discord, OpenAI, xAI voice paths) is independent of the headline story. Skip if you do not run OpenClaw realtime voice.
• The macOS Gateway switching fix is independent of the headline story. Skip if you do not run the macOS Gateway.
• The literal chat content fix (TTS directives literal in Markdown code, attachment hints out of command input) is independent of the headline story. Skip if neither TTS nor command-attachment-hints is part of your deployment.
• The 1,247-PR contribution record is not the headline; this article's 22 fix bullets are the user-impact items. Skip the full PR enumeration unless you are auditing a specific area.

Sources

• OpenClaw v2026.9.3 release notes — https://github.com/openclaw/openclaw/releases/tag/v2026.9.3 (verified 2026-09-08 ~14:08 UTC; 22 fix bullets, upcoming-deprecation paragraph, 1,247 unique-PRs count, and v2026.9.1 baseline-exclusion list captured verbatim from the release body)
• OpenClaw atom feed — https://github.com/openclaw/openclaw/releases.atom (entry tag:github.com,2008:Repository/1103012935/v2026.9.3, updated 2026-09-08T09:26:04Z)
• v2026.9.2 stable cross-reference — https://mr.technology/payloads/openclaw-v2026-9-2-chat-perf-reliable-upgrades-gpt-6-astra-swarm-default-sep-2026 (published 2026-09-06 14:08 UTC; defines which features belong to v2026.9.2 vs v2026.9.3)
• v2026.9.1 stable cross-reference — https://mr.technology/payloads/openclaw-v2026-9-1-stable-mermaid-skill-library-update-rollback-sep-2026 (published 2026-09-03 20:08 UTC; defines which features belong to v2026.9.1 vs v2026.9.2 vs v2026.9.3)

Article History

Originally published: 2026-09-08 14:08 UTC

Last verified: 2026-09-08 14:08 UTC

No corrections at this time.