OpenClaw just shipped v2026.3.31 — and if you're managing multiple instances, version pinning matters more than ever.
This release includes security hardening (dangerous-code detection now fails closed by default), gateway fixes for QR bootstrap onboarding, and Android 15+ compatibility. But here's the catch: OpenClaw releases every 1-2 days with breaking changes. If you're running @latest, your bots can break without warning.
Why Version Pinning Matters
I run three OpenClaw instances on a single Mac. When one of them auto-updated mid-conversation and crashed the gateway, I learned the hard way: never run @latest in production.
ClawFleet solves this by pinning a tested OpenClaw version in every release. The current recommended version is 2026.3.23-2 — tested end-to-end before shipping. When you install via the one-command setup, you get this exact version:
curl -fsSL https://clawfleet.io/install.sh | sh
What v2026.3.31 Changes
Key changes for self-hosters:
Security: Install-time scan failures now fail closed by default. Plugins with dangerous code findings require explicit override flags. This is good — it means your bots won't silently install compromised skills.
Gateway: QR bootstrap onboarding restored. If you use the mobile app to pair with your instance, this was broken in 3.28-3.30.
Agent workspace: Files panel now auto-loads workspace files on first open. Minor UX improvement but useful if you're monitoring what your bots are working on.
Chat commands:
/steerand/redirectnow work from the command palette. Useful for mid-conversation adjustments without restarting.
Should You Upgrade?
If you're using ClawFleet: Wait. We'll test v2026.3.31 and bump RecommendedOpenClawVersion in the next release if it's stable. Your instances are safe on 2026.3.23-2.
If you're running OpenClaw directly: Read the full changelog before upgrading. Back up your ~/.openclaw directory first.
If you haven't started yet: Don't worry about versions — ClawFleet handles it for you. One command, tested version, browser dashboard.
The Bigger Picture
OpenClaw's rapid release cadence is a feature for the project but a risk for self-hosters. Every week brings new capabilities, but also potential breakage. ClawFleet's core value is shielding you from this: we test each version, pin the stable one, and let advanced users opt into newer versions through the dashboard's build flow.
If you're running a fleet of bots that your team or customers depend on, version stability isn't optional — it's the whole point.
If this breakdown was useful, a reaction helps others find it too.
Star ClawFleet on GitHub — helps others find the project.
Join the Discord — get help, share your setup.
Top comments (0)