OpenClaw v2026.6.9-beta.1: Richer Telegram delivery, operator field notes

The source record for v2026.6.9-beta.1 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

A small field test

01 / Richer Telegram delivery

Source signal. Telegram now sends rich HTML, preserves rich markdown and sticker paths, renders progress drafts and command output more faithfully, and keeps mentions and spooled handlers on the right delivery path.

The operator question around Richer Telegram delivery is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

02 / More dependable agent recovery

Source signal. retries, terminal outcomes, usage after compaction, session history repair, and reply reconciliation now keep more interrupted or partial turns moving toward a visible final result.

Measure More dependable agent recovery after a fresh session and after a reconnect. The record should say what was retained, what was intentionally absent, and which identity requested the recall.

03 / A stronger Codex integration

Source signal. Codex gains automatic plugin approvals, GPT-5.3 Spark OAuth routing, remote-node exec as a dynamic tool, and more reliable app-server teardown and terminal outcomes.

The useful evidence for A stronger Codex integration is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

04 / Standalone official provider plugins

Source signal. external provider packages are now first-class npm releases, externally installed channel plugins load at Gateway startup, and StepFun is intentionally npm-only because its ClawHub package name is unavailable.

Standalone official provider plugins lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

The details that affect a runbook

More capable web and native clients

the Control UI adds a session workspace rail and extension health, iOS adds Watch controls, and Android shows chat context.

The visible promise in More capable web and native clients needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

Providers and auth

add Codex Hosted Search, improve Gemini CLI OAuth behind proxies, and keep external provider onboarding on current choices and package metadata.

The useful evidence for Providers and auth is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Plugins and installs

externalized official providers publish as independent npm packages, Gateway discovers installed channel plugins at startup, and StepFun installs exclusively from npm.

The operator question around Plugins and installs is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Richer Telegram delivery.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

Security and privacy. redact secrets from debug/config output, block internal HTTP session overrides, audit open-DM tool exposure, and retain plugin write ownership checks. Treat the fix as a boundary condition and retain the source wording beside your local result.

Agent and session runtime. retry thinking-only and empty post-tool turns, prevent duplicate hook execution, preserve fresh usage through compaction, and repair partial JSON/history artifacts. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.6.9-beta.1 source record; the release index and model provider reference remain the references to use for migrations and support boundaries.