ClawHosters
by Daniel Samer
4 min read
OpenClaw v2026.5.18 landed on May 18 and it's already running on your ClawHosters instance. This one matters if you care about plugins, voice, or uptime during config changes.
Here's what shipped.
defineToolPlugin and the New Plugin CLI
Building OpenClaw plugins used to mean reverse-engineering the manifest format and hoping your types were right. That's done. The openclaw plugin SDK now includes defineToolPlugin, a typed helper for creating tool-only plugins without touching the full plugin lifecycle.
Pair it with three new CLI commands: openclaw plugins build, validate, and init. Run init, write your tool logic, run build. Manifest metadata gets auto-generated. TypeScript types are baked in, so your editor catches mistakes before you even test.
For ClawHosters users on Balanced or Pro tiers, this means community plugins will probably get better, faster. More contributors can build tools now that the barrier is lower. And if you're building your own custom tools, the defineToolPlugin pattern saves real time.
TTS Directives Actually Work Now
Voice notes had a problem that was easy to miss. OpenClaw TTS directives like [[tts:voiceId=...]] were supposed to be processed before message delivery. They weren't. In message-tool rooms and proactive sends, the raw directive text leaked straight into the conversation. Your users saw [[tts:voiceId=alloy]] instead of hearing a voice note.
Fixed. TTS directives now get stripped and processed before the message hits any channel. If you've got voice-enabled agents, they should feel noticeably cleaner.
Gateway Restarts Without the Crash
This fix is subtle but important. When a config change triggered a gateway restart, the old process could spawn a detached child that held onto the port. Next restart? EADDRINUSE. The gateway crashes, your agent goes offline until someone manually kills the orphan.
OpenClaw v2026.5.18 switches to in-process restarts by default. Pending replies drain before shutdown. Plugin-service and channel sidecars start in parallel during boot. The result: openclaw faster restarts with shorter maintenance windows and no more orphan process crashes.
For ClawHosters instances, this translates to less downtime during automatic config updates. Probably not something you'd notice unless you were watching logs, but it's the kind of fix that prevents 2 AM alerts.
WhatsApp QR Login via Admin HTTP RPC
A programmatic WhatsApp QR pairing flow now exists via admin HTTP RPC. Right now it's an API-level feature. For ClawHosters, this lays groundwork for dashboard-driven WhatsApp connect, meaning you won't need CLI access to pair a WhatsApp number in the future.
Not live in the dashboard yet, but the plumbing is there. We'll post when it ships.
If you're self-hosting and want to skip the update treadmill, ClawHosters plans start at $19/mo with automatic updates. Your instance is already on v2026.5.18.
