OpenClaw releases 2026.5.22 with ~5ms /models startup
OpenClaw 2026.5.22 shipped leaner gateway and model startup paths, bringing /models to about 5 ms, while also adding locked dependency shrinkwraps and safer Windows rollbacks. That matters because it targets both startup latency and release-install trust for local agent operators.

TL;DR
- OpenClaw says 2026.5.22 makes gateway and model startup paths leaner, with
/modelsdown to about 5 ms, according to openclaw's 2026.5.22 release post and the linked release notes. - The same release adds generated shrinkwraps for the root package and OpenClaw-owned npm plugins, a supply-chain hardening change that openclaw's install-trust thread pairs with earlier package acceptance and slimmer runtime tarballs.
- Windows got another round of repair work: openclaw's Windows update thread says native runs now use safer npm and pnpm shims, portable Git and Node bootstrap paths, and rollback when git-backed updates fail.
- Operator-facing UX also moved: openclaw's chat picker update adds search and Load More pagination for older sessions, while openclaw's verbose-mode update extends
/verbose onto channels and forum topics.
The release notes are short, but the thread points to the real pattern: faster model metadata fetches, tighter npm packaging, and another pass at Windows install weirdness. You can also jump straight to the older installer docs, the model concepts page, and the doctor docs because this update mostly sharpens paths OpenClaw already exposed.
Startup paths
The headline number is /models at roughly 5 ms. OpenClaw frames that as part of “leaner” gateway and model startup paths, so this looks less like a new feature ship and more like latency shaved out of the control plane.
That lands a few days after openclaw's model status note added clearer explanations when a session is pinned to a model other than the default, with a docs link to the models concept page. Between the two updates, the model surface is getting faster and less opaque.
Release trust
OpenClaw broke the packaging changes into three concrete pieces:
- generated shrinkwraps for the root package
- generated shrinkwraps for OpenClaw-owned npm plugin packages
- package acceptance earlier in the pipeline, with docs and assets kept out of runtime tarballs
Those are boring changes in the best way. They target dependency drift and install-time surprises, not headline capability.
Windows repair paths
Windows fixes make up a big chunk of the recent release cadence. In 2026.5.22, OpenClaw says native Windows runs now use safer npm and pnpm shims, portable Git and Node bootstrap paths, and rollback when git-backed updates fail install, build, or doctor repair.
That follows the 2026.5.20 patch where openclaw's earlier installer follow-up said installs no longer visibly froze at “Starting setup...” and managed updates stopped silently switching Node binaries. The pattern is clear enough: Windows reliability is getting patched in small, operator-facing increments.
Session and debug surfaces
The control UI chat picker now has search plus Load More pagination, which keeps initial session loads bounded without burying old conversations.
/verbose on also now works across direct chats, groups, channels, and forum topics, exposing tool and progress summaries in more places. That is a small feature, but it introduces new information at exactly the layer people use when they are trying to understand what an agent just did.