OpenClaw 2026.6.8 is now the stable release, promoted Tuesday afternoon after the beta train that OpenClaw Chronicles covered earlier today. The stable tag landed at 16:32 UTC with npm package verification, registry integrity data, plugin publishing, Windows Hub promotion, and macOS signed/notarized asset workflows.
That distinction matters. The morning beta story was about the feature set. The stable release is about availability and trust: the same broad channel, provider, runtime, usage, UI, and memory work is now published as the current package and backed by the release evidence operators expect before upgrading production agents.
What Shipped
The 2026.6.8 release is wide. Its headline is still richer message delivery across Telegram and WhatsApp, including structured Telegram output, preserved intentional line breaks, richer final replies, safer rich-media boundaries, and WhatsApp ACP binding support.
The release also tightens agent and gateway recovery. The notes call out account-scoped direct sends, generated media completions, auto-reply final replies, restart shutdown aborts, yielded subagent pause handling, reset archive fallback reads, heartbeat dedupe, session identity prompts, and rejection of unknown OpenAI agent selectors.
Provider handling is another major theme. OpenClaw adds GLM-5.2 support and Claude Haiku 4.5 catalog rows, normalizes provider-qualified IDs for OpenRouter and Google Vertex paths, routes OAuth image defaults through Codex where eligible, bounds model browsing, preserves storeless OpenAI Responses replay compatibility, and quarantines unreadable or post-hook tool schemas for OpenAI and Anthropic-family providers.
Stable Means More Than a Tag
The release proof is unusually useful for operators. The notes link the npm package, registry tarball, integrity hash, release SHA, release publish workflow, npm preflight, full release validation, plugin npm publishing, plugin ClawHub publishing, OpenClaw npm publishing, Windows Hub promotion, macOS signed/notarized preflight, Swift validation, macOS asset promotion, and stable appcast PR.
That is the difference between "new code exists" and "this is safe to evaluate as a packaged upgrade." OpenClaw deployments often sit behind chat channels, local agents, cron jobs, mobile nodes, and private integrations. A stable release with downstream publishing evidence reduces the number of moving pieces an operator has to verify manually.
The npm registry also reflects the promotion: 2026.6.8 is now the latest package, while 2026.6.8-beta.2 remains the beta tag.
Operator Takeaways
For chat-heavy deployments, the channel work is the most visible change. Telegram output should preserve more structure, while WhatsApp ACP bindings make configured assistant-control paths less brittle.
For model-heavy deployments, 2026.6.8 is mostly about safer edges: provider prefix normalization, catalog updates, SecretRef-aware model auth, reasoning signature recovery, and tool-schema quarantine. None of those is flashy by itself, but together they reduce the odds that a provider quirk turns into a broken or over-broad agent call.
For desktop users, the macOS and Windows proof links are the practical upgrade signal. The release includes DMG and ZIP assets, stable appcast work, and Windows Hub promotion rather than just the core npm package.
Read the full release notes here: OpenClaw 2026.6.8.