NEW OpenClaw Update is HUGE!

Summary

The OpenClaw 3.13 update is a substantial maintenance and hardening release with over 60 changes from more than 20 contributors. While there are no flashy new AI features, the improvements you get here are the kind that make your day-to-day use significantly more reliable and efficient. If you use OpenClaw for browser automation, you will notice a major difference. Batch operations now work predictably, failure handling is more robust, and stale session errors are a thing of the past — meaning your long-running workflows will finally stay stable. On mobile, the Android chat settings UI has been redesigned, Google QR code scanning is natively integrated, and iOS users get a proper onboarding welcome screen. Small changes, but they add up to a more polished experience, especially if you are rolling OpenClaw out to non-technical users. For those of you running Docker in production, you now get timezone control via an environment variable, a closed security hole that previously leaked gateway tokens during builds, and improved restart handling — all of which means fewer manual interventions on your end. Messaging platform users also get meaningful updates. Slack gets interactive reply directives, Telegram gets IPv4 fallback for media downloads, Discord now recovers gracefully from gateway failures instead of crashing your agents, and Fei Shu users get event-level deduplication to eliminate the double-message bug. For model and agent configuration, your explicit model settings will no longer be overridden by defaults. Ollama users can now toggle internal reasoning output on or off, and Gemini normalization extends to the Google Vertex provider. Perhaps the most celebrated improvement is the roughly 50% memory reduction. If you are running OpenClaw on a local machine, mini PC, or a cost-sensitive cloud instance, this is transformative. Previous versions were silently consuming RAM during long sessions, making your agents progressively slower and less reliable. This release addresses that through plugin SDK deduplication, improved cron isolation, and better gateway resource management. Additional fixes include dashboard performance improvements, proper formatting of large chat replies, critical bug fixes for cross-agent sub-agent spawns, and cleaner plugin and configuration schema validation that will save you hours of debugging.