OpenClaw v2026.6.6-beta.2: Reliable Telegram delivery, interface notes

v2026.6.6-beta.2 changes a surface that users can see. The release record describes a channel, client, interface, or browser change; this article follows the state behind the screen instead of treating a new button as proof that the workflow is complete.

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

State that a reader can see

01 / Tighter security boundaries

Source signal. transcript, sandbox, MCP, browser, channel, and exec-approval paths now fail closed around unsafe access, timed-out approvals, and malformed boundary input.

Treat Tighter security boundaries as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

02 / Reliable Telegram delivery

Source signal. account-scoped topics route to the correct agent, streamed text survives tool calls, callbacks and draft chunks stay coherent, and unauthorized DM text does not enter cache or prompt context.

Before widening access for Reliable Telegram delivery, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

03 / iMessage stays connected

Source signal. always-on inbound recovery, durable echo markers, block streaming, idle approval discovery, and outbound transport now survive restarts and idle periods.

Before widening access for iMessage stays connected, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

04 / Better browser and MCP connectivity

Source signal. existing browser sessions, CDP/WebSocket discovery, default-profile URLs, OAuth/SSE transport, and tool schemas now connect through clearer, safer paths.

Read Better browser and MCP connectivity as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

The wiring behind the screen

Faster first replies

Control UI startup no longer waits on broad model loading, while cached metadata, lazy slash-command work, and first-event tracing make slow initial responses visible.

The safe reading of Faster first replies is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

CLI progress

emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding.

Use CLI progress as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

Observability

allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies.

Read Observability as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Tighter security boundaries.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

Agent/session recovery. drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. Record the failure that this correction addresses before declaring the upgrade complete.

User-visible content boundaries. suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native /compact replies through source suppression. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.6.6-beta.2 GitHub release. The release index gives the surrounding sequence, while the channel routing guide supplies the operational background.