OpenClaw v2026.3.13-1: Telegram fix, for maintainers

For maintainers reading v2026.3.13-1, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

Stable status describes the release line, not every local provider or channel. Check the version-specific notes before upgrading. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Compatibility for maintainers

API, package, and test clues

Read the narrow change in context

v2026.3.13-1 is a stable checkpoint with a deliberately small surface. The source names Compaction fix: use full-session token count for post-compaction sanity check. A narrow patch still has a clear job: it should remove one failure or preserve one compatibility promise without changing unrelated configuration.

Keep this patch beside the package and test record. Compare the installed tag, package version, and service owner before applying it. If this entry is a correction release, record the broken behavior that led you here, then repeat that exact scenario after the update. That evidence is more useful than a general claim that the package installed successfully.

The adjacent source detail is Telegram fix: thread media transport policy into SSRF. Read both signals together, because a hotfix can alter the boundary around a plugin, channel, session, or installer even when the version number looks like a minor suffix.

A small worksheet for this version

• Write the old version, the new version, and the package or tag that actually changed.
• Capture one reproduction before the update and the same reproduction after it.
• Record the first useful log line, the final user-visible result, and any rollback command that was tested.
• Leave unrelated channels, skills, and provider defaults untouched until the correction is understood.

Run the smallest useful rehearsal

1. Write down the baseline for Compaction fix, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Keep the full v2026.3.13-1 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.