ClawHosters
by Daniel Samer
3 min read
Already live on your ClawHosters instance. Nothing to do on your end.
This one is a hotfix. OpenClaw v2026.3.22 shipped with packaging bugs that broke the dashboard UI (503 errors) and left the WhatsApp standalone plugin out of the npm bundle entirely. v2026.3.23 fixes that, plus 49 other issues across authentication, messaging, and LLM configuration. 16 contributors involved.
Here is what actually matters in this openclaw v2026.3.23 release.
ClawHub Auth Path Fix
This was a sneaky one. ClawHub silently fell back to unauthenticated mode when it couldn't find your credentials on macOS (the Application Support path wasn't checked) or on Linux systems using non-default XDG directories. You'd browse skills, try to install a gateway plugin, and get permission errors with no obvious explanation.
Both paths are now honored. If you've been having trouble installing ClawHub skills or gateway plugins, this is probably why.
Mistral Config Doctor
If you've been running a Mistral model with OpenClaw, your config might have context-sized output limits. That's a problem. It means your agent could burn through tokens at a rate that makes no sense for the actual task.
The new openclaw doctor --fix command detects old Mistral configurations and lowers max-token defaults to safe output budgets. Run it once. It takes about two seconds. For ClawHosters customers, Mistral configs are managed on the server side, so this mostly matters for self-hosters who configured their LLM provider manually.
Messaging Platform Fixes
Discord, Slack, Feishu, and Telegram all got attention in this openclaw update march 2026:
Discord and Slack: Components and blocks are optional again. Pin, unpin, and react flows stopped failing schema validation.
Feishu: File and image attachments now route through the outbound media path instead of breaking silently.
Telegram: Threading in group chats and DM topic handling both got fixes.
If your agent talks to users through any of these platforms, the experience just got more reliable.
Web Search and OAuth
Two smaller fixes worth knowing about. Agents now use whatever web search provider is actually active at runtime instead of sticking with a stale default. And if you're using OpenAI Codex through a proxy, expired OAuth profiles can finally refresh without manual intervention. The same fix applies to MiniMax OAuth.
For the full changelog, check the official release notes on GitHub. If you're self-hosting, update now. On ClawHosters, you're already running it.
