OpenClaw v2026.5.18 landed on May 18, 2026 at 1:54 PM America/Chicago time, which was May 18, 2026 at 18:54 UTC. This stable release is not about showing off. It is about making OpenClaw easier to trust when you restart it, extend it, and depend on it to actually deliver the finished answer.

The center of gravity here is operational smoothness. Restart traces got more informative, plugin scaffolding is cleaner, browser dialog handling is better, and a lot of reply-path and session-state weirdness got cleaned up. If you run OpenClaw on real channels instead of only poking at it locally, that matters more than another flashy demo feature.

What users can now do

Build plugins with less ceremony. OpenClaw now has a cleaner typed workflow for simple tool plugins, including build, validate, and init commands. That gives custom-tool authors a more obvious path from idea to working plugin.

See browser blockers sooner. Dialog handling got better, which means browser tasks are less likely to look mysteriously frozen when the real problem is a modal waiting for input.

Spend less time interpreting restart behavior. Gateway startup and restart tracing keep getting clearer, especially around where time is actually going. That helps when you are debugging a reload in production and need facts instead of vibes.

What got safer or less annoying

A big chunk of this release is quality-of-life hardening: reply delivery stays intact more reliably, approval and async execution paths are less brittle, session routing gets safer, and several provider or channel-specific failures now fail in more honest ways.

There is also a lot of polish for the Mac app, better QA coverage around runtime parity and tool fixtures, and a long tail of fixes across Telegram, Codex, subagents, media handling, and config validation. It is exactly the sort of stable release I like seeing after a busy beta stretch.

One practical note before you update hosts pinned to Node 22: the minimum supported Node.js 22 line is now 22.19.

What I would test right after updating

1. Do one real restart or config reload. Confirm your actual channels, sidecars, and sessions come back the way you expect.
2. Run one browser task with a login or confirmation step. Make sure dialog handling feels less opaque.
3. If you maintain plugins, initialize one small test plugin. You want to see the new flow yourself before you need it under deadline pressure.
4. Send one real end-to-end reply in the channel that matters most. This release includes several fixes in the class of bugs where the final answer used to vanish or route badly.
5. Verify Node.js 22.19 or newer on Node 22 machines. That is the first thing I would check if a host behaves differently after the update.

Should you install this release?

Yes. If you wanted a stable cut that makes OpenClaw calmer and more predictable in daily use, this is that kind of release.

It is not the loudest update. It is the kind that saves you from a pile of small headaches later, which is usually a better trade.

---

Full changelog: View on GitHub