Release desk
The newest beta channel prerelease bundles model-runtime updates, first-run setup continuation, CDP relay for paired Chrome sessions, verified external Gateway supervision, and compact SQLite backup and restore commands — with publication evidence operators can check themselves.
Long-lived Codex child agents lost OpenClaw hook policy when their parent turn ended, failing later tool calls with 'native hook relay not found'. The merged fix introduces per-turn immutable relay bindings that survive cross-turn polling without granting session-wide authority.
A merged PR deletes the hardcoded two-session cap per paired node. Capacity now defaults to one worker session per available CPU core (clamped to 1024) with an explicit config override — a significant change for anyone distributing session load across machines.
Agents could not discover platform custom emojis: the reaction emoji parameter was undocumented and emoji-list was invisible to the model. A merged feature makes custom-emoji discovery a first-class, gate-aware capability across the three major channels.
Backward NTP corrections could make Gateway shutdown wait indefinitely for automation runs; forward jumps could cut grace periods short. A merged fix bounds drain waits with native timers instead of the adjustable wall clock.
August 23 merges add a macOS-only realtime Gateway relay for Talk, surface its settings in the Control UI, and fix a /v1/responses defect that returned blank or clipped assistant output while chat-completions stayed correct.
When the message tool failed with proven-not-sent evidence, both the durable outbound queue and the model held the same retry, so recipients got two copies seconds apart. Merged fixes make the queue the single retry owner, including remote Gateway deployments.
OpenClaw main adds plugin-declared selectable context windows with a 200K/1M switch in the Control UI model picker for Claude 5-series models, session-level validation, and explicit argv/env mapping.
A same-day trio on main and the pinned release: Codex sessions gain approved paired-device support, newly available account models work before the provider catalog updates, and the release branch gets the backport.
Compaction dropped real user turns, a watchdog killed active turns mid-flush and forgot queued replies, and /restart looped forever — all three merged to main on August 21.
A pruning inversion deleted eligible sessions, an ingress watchdog dead-letted timed-out Telegram messages with attempts=0, and recovery erased queued deliveries during transient adapter outages — all three are fixed on main.
The managed @openai/codex runtime floor moves to 0.149.0 with Doctor as the sole migration owner for the retired untrusted approval policy, alongside same-channel durable async delivery and three release-branch backports.
The Control UI can deep-link retained run evidence, keep new-session preferences private to an identified operator and clone GitHub repositories into Gateway-managed projects.
New suspend/resume CLI controls remove a control-plane dead end, while /startupz separates traffic admission from downstream channel health and repairs bundled deployment templates.
Document, image, audio and video intake now records bounded model-visible outcomes when an attachment is unsupported, unselected, disabled, unreadable or fails processing.
A same-day routing correction makes an unset heartbeat target resolve to a configured operator DM, never a group, while failed work remains pending and stream history is finalized before alerts.
The Meta provider gains Muse Spark 1.2 and a discounted Contributor variant; operators must keep confidential and personal data off the Contributor tier.
Merged fixes stop blind final-reply replay, record ambiguous delivery as durable notice debt, resume interrupted main sessions and preserve long-session context progress.
The update path now handles live terminals deliberately, avoids duplicate plugin installation, verifies launchd restart and reports the real result in Control UI.
Merged Slack changes carry the originating Enterprise Grid workspace through actions, slash commands, events and native approvals instead of trusting ambiguous channel or user IDs.
The QMD backend, its configuration and its process/runtime surface are gone from OpenClaw main. Doctor can remove retired settings, while plugin authors also lose the withLease state API.
The extended-stable selector moved to 2026.6.34 with security, delivery, provider and local-runtime hardening. Here is the operator decision, the migration warning and what to verify.
Embedded agents now block a critical loop batch, permit one corrective model response and terminate a second critical loop in the run.
The package, plugin and provider names are now deliberately distinct, with guarded migration for legacy official installs.
The reviewer now prefers bounded edits to existing skills, drops regex chat capture and keeps risky rewrites pending for operators.
Doctor and status now report redacted exporter health, while plugin-hosted LLM completions gain trusted usage attribution in OTel.
A merged classifier fix prevents ambiguous bodyless provider 400 responses from being treated as context overflow, avoiding pointless compaction and retry.
A P0 session-maintenance fix makes 0 disable disk cleanup, while a related reset fix prevents old model context returning after inference failure.
Merged fixes make fresh CLI processes load the configured memory provider and carry prepared OAuth context into authenticated CLI-agent tool grants.
Merged auth fixes prevent ambient environment keys from silently taking declared-profile traffic and add persistent billing/auth cooldowns for inline provider keys.
Merged CLI fixes make gateway call honor a custom local port and stop externally supervised status checks from being retargeted by unrelated native-service metadata.
The SMS plugin can now receive and send MMS, record signed carrier delivery outcomes and retry transient media failures without silently losing attachments.
A merged plugin SDK and Gateway change canonicalizes route identity, checks every overlap and lets required webhook owners fail startup explicitly.
Headless operators can now dry-run, archive and delete exact session keys through Gateway-backed lifecycle commands without editing SQLite.
Merged Control UI fixes recover interrupted onboarding, repair post-upgrade pairing and enforce origin checks for Tailscale-authenticated avatar reads.
Merged cron changes auto-disable repeated failures, harden delivery and preserve exactly-once scheduling across DST folds and historical timezone transitions.
Three merged browser fixes keep shared-tab sessions alive after extension reloads, wake queued shares without periodic heartbeats and permit page extraction in tab-bound runs.
The seventh 2026.7.2 beta adds Telegram directive validation and concurrent-ingress session repairs, but does not include later Aug 2 main-branch fixes.
Merged cron fixes normalize zoned ISO and end-of-day times, while web and macOS editors preserve advanced delivery settings during clone and save.
Remote setup now probes password-only Gateways with target-bound credentials, while macOS onboarding keeps its auth gate, token recovery and config-conflict protections.
Merged cron fixes restore primary webhook delivery records, replay subsecond restart misses, preserve failure-alert account ownership and link tasks to the right transcript.
Three merged fixes add deadlines and dispatch provenance to node-hosted exec, then report ambiguous outcomes instead of risking duplicate side effects.
Merged accounting fixes preserve cached, cache-write and reasoning usage in the Responses API and honour operator-configured Anthropic model pricing.
Two merged Linux service fixes preserve quoted and backslash-containing values and parse every inline Environment assignment before Gateway startup.
The npm beta tag now points to beta.6, packaging more delivery, session and upgrade fixes while later task, memory and realtime repairs remain on main.
A P1 Codex repair and four related fixes stop incomplete turns looking successful, destructive steer retries, truncated exec recovery and unsafe terminal tool calls.
The Automations terminology stack has landed on main with a permanent cron compatibility alias, a new CLI alias and intentionally unchanged RPC, config and schedule syntax.
A new main-branch inference contract gives plugins a fresh, text-only model call with zero tools, explicit model authorization and fail-closed runtime support.
Two merged main-branch fixes stop accepted WhatsApp work being deleted under queue pressure and let dropped queued runs return to durable ingress for retry.
Two merged main-branch fixes tighten Gateway service ownership: shell overrides no longer rewrite a managed service, and macOS refuses competing launchd managers.
Merged Memory Core and LanceDB fixes preserve rollback compatibility, make legacy backfills re-applicable, and extend recall cooldown protection to prompt building.
Main now carries four material operational fixes that beta.5 chronology cannot contain. Operators should match the fix to their failure mode, not assume the prerelease has it.
A merged Memory Core change closes cross-project recall leakage in curated files, while a separate fallback keeps keyword recall available when embeddings cannot start.
A main-branch fix replaces multi-megabyte per-session pricing fingerprints after beta.5 Gateways were shown consuming gigabytes while loading Usage rollups.
A merged main-branch fix makes durable-ingress availability part of channel health after a production Slack gateway hid more than 26 hours of dead inbound delivery.
The new OpenClaw beta packages a large state-safety and durable-delivery release. Production operators should stage recovery, channel and schema tests first.
A merged main-branch fix preserves real Promise settlement order, drains dispatched tools safely and keeps suspended Code Mode execution attributable.
A merged main-branch P1 fix detects stable no-progress tool output across changing arguments, closing a gap in exact-call loop detection.
A merged main-branch fix adds bounded retention for trajectory runtime events after live rows consumed 85% of one long-lived agent database.
A merged browser automation contract prevents stale-document actions, marks snapshot deltas and exposes structured output. The safer behavior still requires caller changes.
A main-branch fix restores global webhook and chat failure destinations while preventing duplicate or cross-channel notifications. Operators should test forced failures after upgrade.
Merged main-branch work brings Ollama and llama.cpp preparation into web/macOS onboarding and constrains setup-planner JSON on supported backends.
OpenClaw now defaults GPT-5.5 and GPT-5.6 sessions to a 272,000-token runtime budget while preserving a deliberate long-context path for operators who accept the higher tier.
OpenClaw now supports Claude Opus 5 and promotes it for new Anthropic setups on main. Packaged operators should wait for a release that includes the merge.
New main-branch code converts heartbeat tasks into cron jobs, but adjacent fixes show why source-build operators need a full state backup and a post-fix revision.
A merged main-branch change replaces workspace HEARTBEAT.md files with revision-safe cron scratch; existing operators should use Doctor rather than migrate by hand.
How OpenClaw added channels, staged package swaps and service-aware updates before June 23, 2026.
OpenClaw 2026.7.2-beta.3 can delete trimmed transcript rows while printing a nonexistent archive marker; a merged main-branch fix is not packaged yet.
Merged fixes target Linux Codex hook process leaks, tools that ignore aborts, and Gateway RPCs that continued after cancellation—but no current npm channel contains them yet.
OpenClaw 2026.7.2-beta.3 adds remote coding, cloud workers, external Gateway supervision and Linux packaging. Here is what operators should test.