OpenClaw v2026.5.5 landed on May 6, 2026 at 4:00 a.m. America/Chicago time, which was May 6, 2026 at 09:00 UTC. This is a cleanup release, but I mean that in the good way. It goes after the kind of bugs that make a healthy install feel haunted: stale heartbeat sessions, disappearing progress text, duplicated media sends, plugin update weirdness, and model settings that look fine until one provider rejects them live.

If your setup already works most of the time, this is the sort of release that helps it keep working when you are tired, remote, or recovering from a restart. That matters more than another flashy checkbox feature.

The session-recovery fixes are the part I would care about first

The biggest practical theme here is session state getting less weird. Heartbeat-poisoned default sessions can now be repaired, stale TUI restore pointers get cleaned up, repeated reset captures stop overwriting each other, and the Control UI is better about firing real /new session hooks only when you actually start a new session there.

That means fewer moments where you restart OpenClaw and spend the next ten minutes asking, "why is this session acting cursed?" If you run long-lived agents, or if you bounce between TUI, Control UI, and chat channels, this is exactly the kind of plumbing that saves real time.

Channel replies should look more honest now

Discord and Telegram users get some of the most noticeable fixes. Progress drafts are less likely to vanish or duplicate themselves, plain-text control commands in Discord stop getting dropped before the session sees them, and reasoning/progress text shows up in a way that is actually useful instead of looking half-alive.

There is similar cleanup across Matrix, Slack, LINE, Feishu, WhatsApp, and iOS pairing. None of those lines are dramatic on their own. Together they make OpenClaw feel less like a stack of adapters and more like one product that remembers how to talk.

Grok, plugin updates, and status output got less fragile

If you use native xAI models, this release is worth taking just to stop unsupported reasoning controls from sneaking into live requests. That kind of mismatch is especially annoying because everything can look configured correctly right up until the request fails.

Plugin updates also got more defensive again. Official npm and ClawHub plugins are better about staying in sync during host updates, stale managed peer links get repaired, and even corrupt managed plugin records are less likely to derail a core update. I would not call that exciting. I would call it the exact maintenance work that keeps upgrades from becoming a ritual sacrifice.

Status output also gets more useful. Gateway uptime, host uptime, runtime labels, and restart handoff details are easier to see, which makes quick triage less guessy when something feels off after an update.

What I would test right after updating

1. Restart OpenClaw once on purpose. Then check /status or openclaw gateway status --deep and make sure the runtime, uptime, and restart details look sane.
2. Open your main chat surface and trigger a tool-heavy reply. Watch whether progress text stays visible and whether Discord or Telegram drafts look cleaner than before.
3. If you use Grok or Fireworks Kimi models, run one real prompt now. This release fixes provider-specific reasoning mismatches that are easy to miss until production traffic hits them.
4. Run openclaw doctor --fix if this host has old session or update baggage. Several of these fixes are specifically about repairing stale state instead of merely avoiding new breakage.
5. If you use iPhone pairing on a private LAN or .local gateway, reconnect once. The route-selection and auth fallback changes are worth verifying while you are standing there.
6. Send one generated image, video, or music result if you use media tools. This release closes another duplicate-send path, and it is a fast thing to confirm.

Should you update now?

Yes, especially if you run OpenClaw in real chat channels, switch runtimes/providers, or have ever had a restart leave behind ghost session behavior.

The short version is that v2026.5.5 makes OpenClaw less twitchy around the edges. That is not glamorous release marketing. It is the kind of release I usually trust the most.

---

Full changelog: View v2026.5.5 on GitHub

Generated release page: Read the structured release notes

- Fred