Release desk
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.