OpenClaw v2026.5.7 landed on May 7, 2026 at 3:57 p.m. America/Chicago time, which was May 7, 2026 at 20:57 UTC. If you run OpenClaw in real channels, keep cron jobs around for days, or babysit plugin-heavy installs, this is the kind of release you feel after a week. It removes failures that used to show up late, after the first false success already fooled you.

The big theme here is not one flashy feature. It is trusting the plumbing a little more. Channel sends route to the place you meant. Cron tooling tells outside scripts what state a job is actually in. Update and repair paths do less damage while they are trying to help.

Channel delivery gets less slippery

A few of the highest-value fixes are about messages that looked valid but could still land wrong or report success too early. Discord now treats provider-prefixed targets like discord:channel:<id> as channel sends instead of confusing them with DM targets. WhatsApp gets better at proactive sends to LID-addressed contacts. Telegram is stricter about sender allowlists and better about telling the truth when a same-chat outbound send really did succeed.

That is practical, not cosmetic. If you run cross-channel agents or scheduled follow-ups, fewer messages should disappear into a routing mistake that only becomes obvious when a human asks where the alert went.

Cron and status output finally tell external tooling more of the truth

openclaw cron list --json and openclaw cron show --json now include computed status directly. That saves every wrapper script from reverse-engineering whether a job is disabled, running, idle, skipped, or broken. There is also a good fail-fast fix here: recurring jobs that try to announce through delivery.channel=last without a previous route now stop before burning model tokens on a run that could never deliver.

The repair path also got sharper. openclaw doctor --fix can clean up persisted cron jobs carrying junk model overrides like "default", blank strings, or JSON null. That kind of data rot is boring right up until it breaks the one job you forgot was still important.

Updates and long-lived sessions should recover with less drama

Plugin publishing now retries transient ClawHub dependency install failures, verifies expected package versions after publish, and does a better job keeping one flaky preview cell from turning a maintenance release into guesswork. Managed plugin install and rollback paths also use the same absolute lifecycle shell, which matters on hosts with restrictive PATH setups.

Long-lived sessions got useful cleanup too. /new and sessions.reset clear cached skill snapshots so changed skills show up again without a weird half-stale view. Transcript rollover persists a fresh transcript file when the session id changes. Cached context views get invalidated when source history shrinks or assembly fails, which closes one more stale-history trap.

What I would test right after updating

1. Run openclaw cron list --json. Make sure the status fields match reality for your scheduled jobs, especially anything disabled or recently failing.
2. Trigger one cross-channel send on purpose. If you use Discord channel IDs, Telegram automations, or proactive WhatsApp sends, verify the message lands exactly where you expect.
3. Start a fresh session after changing skills. Use /new or reset a long-lived session and confirm the visible skill list rebuilt cleanly.
4. Repair or install one managed plugin. This is a fast way to catch hosts that used to fail in npm lifecycle cleanup or restricted shell environments.
5. If you use Telegram polling or Discord voice, do one live check now. The watchdog and voice-capture fixes are worth proving while you are already in maintenance mode.

Should you update now?

Yes, especially if OpenClaw does real work for you across channels or on a schedule. This release cuts down on false-positive success, stale state, and repair tools that make a second problem while fixing the first.

If your install is small and local, you may not notice every line item. If your install touches cron, plugins, chat routing, or long-lived sessions, you probably will.

---

Full changelog: View v2026.5.7 on GitHub

Generated release page: Read the structured release notes

- Fred