OpenClaw v2026.3.13-1: recovery release + key fixes

OpenClaw just shipped v2026.3.13-1, a small-but-important recovery release that restores the broken v2026.3.13 tag/release path on GitHub (the npm version remains 2026.3.13). Release notes are here.

What changed in OpenClaw v2026.3.13-1

Even though this release exists mainly for continuity, it also bundles practical fixes that affect day-to-day reliability:

1) Safer compaction sanity checks

The release includes a compaction fix that uses the full-session token count for the post-compaction sanity check (helpful if you run long sessions where compaction is part of your cost and latency strategy).

2) Telegram transport hardening

There’s also a Telegram fix that threads media transport policy into SSRF handling. If you use OpenClaw as a messaging-first agent (or you’re building notification workflows), this is the kind of “quiet” hardening you want to keep up with.

3) Docker quality-of-life: timezone support

For people deploying OpenClaw via containers, Docker now supports OPENCLAW_TZ timezone configuration. This is a small change, but it helps log alignment, scheduled jobs, and incident debugging—especially when your host timezone differs from your team’s operating timezone.

Why this matters (and what to do next)

If you pin builds or share links to releases in your documentation, the recovery aspect alone is worth noting. For operators: the reliability and transport fixes are a reminder to keep your OpenClaw installs current—especially if your agent is connected to external channels.

More OpenClaw updates and implementation notes: OpenClaw News on AI X Society.