OpenClaw Splits the Release Track as Live Plugins Meet Supply-Chain Risk

A Second Release Lane Changes the Upgrade Decision

2026.7.35 Becomes the Extended-Stable Option

The newest OpenClaw 2026.7.35 GitHub release introduces a gateway-only extended-stable line that the project describes as its current equivalent to LTS. It starts from the late-July codebase, adds critical security, reliability and performance work, and includes newer model support. The feature-leading release remains 2026.9.5.

This first published July maintenance release also repairs a specific upgrade hazard: Doctor now preserves the complete bundled plugin inventory while creating or repairing registry state. It can recover from the partial registry written by 2026.7.34 without discarding external plugin installation records. The release says the backport was selected after auditing 1,418 commits since the previous cursor.

The cumulative notes matter because 2026.7.33 and 2026.7.34 were intentionally not published as GitHub Releases. Their maintenance work is rolled into 2026.7.35, including hardened command parsing, browser-origin checks, safer plugin Git installs, bounded diagnostic and provider reads, message recovery, channel delivery fixes, and stricter handling for malformed node payloads.

That creates a real operator choice. A Gateway that values a slower feature surface can follow the July maintenance line, while deployments needing the newest collaboration, browser, voice and management capabilities can stay current. “Extended-stable” does not mean “ignore updates”; it means security and reliability backports arrive without importing every new feature.

2026.9.5 Makes the Running Gateway More Malleable

Plugins Can Change Without a Full Restart

The current OpenClaw 2026.9.5 release notes document supported plugin installation and reload while the Gateway remains running. Owners can use the CLI, an authorized chat command, or the Plugins interface. Existing consent and permission checks still apply, and managed Codex conversations can continue with refreshed tools inside bounded context after the current native turn and background terminals stop.

This reduces downtime, but it also makes plugin state more dynamic. Batch enable, disable, reload, update and uninstall commands preserve earlier successful changes when a later operation fails, so the resulting state must be reviewed rather than assumed atomic. Saved installations that fail activation still require repair followed by an explicit reload. Hot reloading is an availability feature, not permission to skip change control.

Session Share Adds Deliberately Narrow Collaboration

The bundled Session Share plugin documentation describes a read-only catalog of selected conversation groups exposed to another paired OpenClaw installation. Recipients can see conversation text and eligible user-created forks, but not subagents, tool activity or reasoning; they cannot continue, archive or open a terminal on the shared session.

Both machines must enable the feature, and an empty group selection publishes nothing. That default is sensible because transcript text and metadata can still contain private information. The source operator must choose groups carefully, use a sessions-only command allowlist for the node connection, and remember that revocation cannot erase information already received.

Conversation Archives Add a Backup Obligation

Cold transcript storage can compress inactive history and restore it when a conversation is reopened. It is off by default, while the Settings panel exposes storage use and a manual archive action. The release documentation warns that 2026.9.5 changes the conversation database even when archiving stays disabled, so a downgrade requires the matching older application build and a compatible backup.

The separate OpenClaw backup guide explains why raw copies of live SQLite files are unsafe: the Gateway may be writing while they are copied. Supported backup commands capture committed state, include cold archives referenced by their database, and fail instead of producing a successful but incomplete artifact when an expected archive is missing or corrupt.

Security Practice: Verify the Checkout, Not the Requested Ref

Tool Spotlight: @openclaw/diffs

Community and Ecosystem: Maturity Means Maintaining Two Speeds

The 2026.7.35 notes reveal a community doing maintenance work that rarely headlines demos: preserving plugin registries, bounding reads, repairing retry timing, protecting Unicode boundaries, draining shutdown work and keeping channel messages from disappearing. The feature release, meanwhile, advances live plugins, paired sharing, browser collaboration, voice and specialist teams. Both kinds of contribution are necessary, but they serve different deployment appetites.

Plugin4Shell widens the lesson beyond OpenClaw. Coding agents are becoming package managers, execution hosts and background updaters at once. A marketplace review, commit pin or “official” label is only one layer; the client must prove the artifact it executed, and the runtime must constrain what that artifact can reach. Supply-chain integrity ends at resolved bytes and effective authority, not at metadata.

OpenClaw’s two-track release story is therefore timely. The ecosystem is moving fast enough that restart-free extension loading and cross-machine collaboration are table stakes, while the security research shows how much hidden machinery those conveniences activate. The practical winner will be the platform that lets operators move quickly without losing the ability to identify exactly which code ran, under whose authority, and from which recoverable state.