OpenClaw's Frequent Breaking Changes: Update Procedures and Current Issues

Update Procedures for OpenClaw's Frequent Releases

OpenClaw is shipping breaking changes every 2-3 weeks, with 13 point releases in March 2026 alone. The source provides specific procedures for updating safely.

Before Updating

• Create a backup: openclaw backup create --name "pre-update-$(date +%Y%m%d)"
• If using Docker, pin your image tag instead of using :latest: image: openclaw/openclaw:2026.3.28

After Updating

• Run: openclaw doctor --fix
• Manually test your channels, crons, and skills before walking away
• The --fix flag catches most config migrations but not all

If Something Breaks

• Roll back to your backup
• Check the GitHub issues page for your specific version before trying again

Current Version Issues (April 2026, Version 3.28)

• Localhost authentication changed: local connections now require tokens
• Skill installs fail closed on dangerous-code detections
• Feishu has a config validation regression (#56942)
• Heartbeat model override is broken (#58137): LiveSessionModelSwitch detection forces your heartbeat back to the primary model
• isolatedSession: true on heartbeat doesn't actually isolate (#56941)

Version Recommendations

• If you're on Feishu, hold on version 3.23-2
• If heartbeat cost savings matter to you, 3.23-2 might also be safer until the model override regression is fixed

The source notes that these types of regressions make managed hosting attractive on BetterClaw, as they get caught during testing before release reaches your agent, though self-hosting remains valid.