Version-specific OpenClaw changes that affect operators. Upgrade notes, breaking changes, migration steps, and what to verify before or after updating.
OpenClaw 2026.3.2 changed onboarding tool defaults, ACP dispatch behavior, and the plugin HTTP route API. Here is the practical checklist for operators.
OpenClaw 2026.3.7 now requires gateway.auth.mode when both gateway.auth.token and gateway.auth.password exist. Here is how to check, fix, and validate it.
OpenClaw 2026.4.14 tightens GPT-5.4 turn recovery, improves Telegram forum-topic handling, and fixes Codex and custom-provider edge cases.
ClawCloud now shows the correct OpenClaw version after manual upgrades by checking the running process first, not the old install path.
OpenClaw 2026.3.28 adds xAI Responses API, a config schema command, plugin approval gates, and stricter validation for old config keys.
OpenClaw 2026.3.24 adds image generation model routing, isolated heartbeat sessions that slash token use, loop detection, and removes the legacy bridge config.
OpenClaw 2026.3.13 brings GPT-5.4 and GPT-5.4-pro, a standalone Codex provider, Z.AI/GLM-5, OpenCode, and multi-key rotation for rate-limit resilience.
OpenClaw 2026.3.8 brings local backup tools, gateway restart recovery, Podman/SELinux fixes, and platform cleanup across macOS, Android, and Linux.
ClawCloud now handles Discord and Telegram configuration separately, matching OpenClaw's strict per-channel validation. Plus dashboard improvements.