OpenClaw has shipped v2026.6.35, the final release for the June 2026 Extended Stable line.
The release was published on September 10th at 06:39 UTC and is framed as an LTS maintenance closeout rather than a new feature train. That matters for operators who stayed on the June branch for stability: the headline is not a flashy UI change, but a large set of audited reliability and safety backports selected for long-running installations.
The release notes point primarily to PR #119942, with release packaging covered by PR #120163. OpenClaw says the complete audited record spans 166 merged PRs between v2026.6.34 and the release target.
What Changed
The strongest theme in this release is bounded failure handling. OpenClaw says bundled providers and channel adapters now bound untrusted response bodies, reject oversized inputs before expensive work, and keep recovery paths safer when transports fail.
The same release also calls out long-running delivery reliability. Agent, Gateway, retry, and channel paths now handle cancellation, retries, partial sends, and process-stream failures without losing work or replaying unsafe operations.
For plugin-heavy installations, the release emphasizes bundled-plugin resilience. Local-model, browser, media, and collaboration plugins are described as recovering more cleanly from malformed payloads, timeouts, and transient upstream failures.
The maintenance set includes:
- Response and memory safety across provider, search, embedding, media, and channel integrations.
- Runtime recovery for outbound retry timing, channel lifecycle, abort handling, process I/O, and persisted state.
- Safer browser automation, local tool, workspace-read, and plugin metadata handling.
- More dependable local integrations for local-model discovery, speech, meeting, and collaboration paths.
- A refreshed generated Plugin SDK API baseline for package preflight verification.
Why It Matters
Extended-stable releases are about trust over novelty. Many teams keep production agents on an older branch precisely because they want fewer moving pieces. The tradeoff only works if the older line continues receiving the fixes that protect memory, delivery semantics, and external integrations.
OpenClaw 2026.6.35 is aimed at those deployments. A malformed provider response, oversized channel payload, flaky process stream, or partial outbound send can be enough to destabilize an agent workflow if the runtime treats the failure too optimistically.
The release notes repeatedly use bounded language: bounded requests, capped reads, rejected oversized inputs, preserved recovery, and retained operation outcomes. That is exactly the vocabulary operators want to see in a final LTS patch.
Operator Takeaway
If you are still on the June extended-stable line, this is the release to evaluate before freezing that branch. The official note calls it the final June 2026 Extended Stable release, so future routine fixes are more likely to land on newer trains.
Teams running providers, chat channels, browser automation, local-model discovery, speech, meetings, or collaboration plugins should treat this as a reliability and safety upgrade. It does not introduce a new release-line feature, but it does consolidate months of defensive work into the branch.
The practical question is simple: if your OpenClaw installation depends on long-running conversations, retries, channel delivery, or untrusted external payloads, v2026.6.35 is worth testing now rather than waiting for the next incident to reveal an old edge case.