OpenClaw Adds Revocable Chat Links and Live Browser Viewing in v2026.9.3
The update makes interrupted agent work easier to resume and inspect, but a public sharing link can expose future conversation text until its creator revokes access.
Loading page…
The update makes interrupted agent work easier to resume and inspect, but a public sharing link can expose future conversation text until its creator revokes access.
Listen to this story
OpenClaw’s v2026.9.3 turns conversation sharing into a controlled-but-not-recallable capability: creators and Gateway administrators can issue read-only links that expose current and future text until revoked, though saved copies remain. The release also improves recovery and observability, including live browser-automation viewing, persistent native Mac tabs, faster reconnection, transcript search, and cloud repository work. Users must upgrade to Node.js 24.16.0+ or 26.1.0+; OpenClaw recommends Node 26.
Shared pages omit tools, reasoning, files, images, and executable widgets.
Revoking a link blocks later viewing but cannot recall copies viewers already saved.
The release reports 1,844 pull requests, 40 direct commits, and 190 contributors.
An OpenClaw conversation can now become a read-only webpage for anyone holding a link. Version 2026.9.3 adds that sharing option alongside faster session reconnection and live viewing of browser automation, making agent work easier to resume and inspect after an interruption.
OpenClaw released v2026.9.3 with workflow and reliability changes aimed at continuity. Updates are intended to recover cleanly after interruptions, while sessions reconnect faster. The release also adds saved meeting-transcript search and repository-backed work in the cloud.
Session creators and Gateway administrators can publish a revocable public link to a conversation. Anyone holding that link can read its existing and future text until access is revoked. The separate read-only page leaves out tools, reasoning, files, images, and executable widgets.
The release also makes browser-driven work more visible. OpenClaw says users can watch browser automation live rather than only encounter its results afterward. In the Mac app, native browser tabs remain open when a user switches conversations, preserving those tabs across chat navigation.
Upgrades carry a compatibility requirement. OpenClaw now requires Node.js 24.16.0 or newer on the 24.x line, or Node.js 26.1.0 or newer, and recommends Node.js 26. Users on older runtimes need to upgrade Node before installing this release.
OpenClaw reports 1,844 pull requests, 40 direct commits, and 190 contributors for the release. The practical change for users is a more continuous workflow: sessions can reconnect after disruption, browser actions can be watched, and conversations can be shared with a control that remains limited once text has left the platform.
Loading discussion...
Join the conversation
Share the safeguard that would affect your answer.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.