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.

By 2 min read
OpenClaw Adds Revocable Chat Links and Live Browser Viewing in v2026.9.3
OpenClaw Adds Revocable Chat Links and Live Browser Viewing in v2026.9.3

Listen to this story

The audio brief

About 1:32
0:001:32
Read transcript
OpenClaw’s newest release lets a conversation become a read-only webpage, accessible to anyone holding its link. That link is revocable, but not recallable: until the creator or a Gateway administrator turns it off, viewers can see both the conversation’s existing text and anything added later. Revocation blocks future access through the link, but it cannot erase copies someone has already saved. The shared page excludes tools, reasoning, files, images, and executable widgets, making it narrower than the live session, but still potentially sensitive because future text continues to appear. Version 2026.9.3 also targets interrupted work. Sessions reconnect faster, and users can watch browser automation live instead of seeing only the final result. On the Mac app, native browser tabs remain open when users switch conversations. There’s saved meeting-transcript search, cloud repository-backed work, and a Skill Workshop change that keeps each agent’s learned skills across workspaces. Model settings now support per-account controls and ordering, while Docker setup better preserves project-file ownership. The upgrade has a firm runtime requirement: Node.js 24.16.0 or later on the 24 line, or 26.1.0 or later, with Node 26 recommended. OpenClaw says the release involved 1,844 pull requests, 40 direct commits, and 190 contributors. The key constraint to watch is simple: sharing is convenient, but once conversation text is copied, revoking the link cannot bring it back.

Story brief

3 key points

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

  1. 01

    Shared pages omit tools, reasoning, files, images, and executable widgets.

  2. 02

    Revoking a link blocks later viewing but cannot recall copies viewers already saved.

  3. 03

    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.

  • Skill Workshop now keeps each agent’s learned skills together across workspaces.
  • Models settings adds per-account controls and lets users order supported accounts.
  • Docker setup preserves project-file ownership while repairing writable OpenClaw state, while a Windows startup fallback retains saved service-environment overrides.

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.

Sources

  1. docs.openclaw.aiv2026.9.3 · OpenClaw

Loading discussion...