NEW OpenClaw Update is HUGE!

Summary

The OpenClaw 2.26 update is primarily a stability release, and it tackles some of the most frustrating issues you've likely been hitting if you've been running OpenClaw for any amount of time. The biggest fixes are around cron jobs, which are the backbone of what makes OpenClaw different from a standard chatbot. If your cron jobs have been firing twice, blocking each other, hanging when manually triggered, or slowly drifting off schedule, this update directly addresses all four of those problems. Fixes include queue drain reliability to prevent silent failures on restart, a raised safety timeout so longer agent sessions don't get killed at the 10-minute mark, and proper backlog clearing when you use the /stop command so context doesn't bleed between channels or sessions. On the security side, the headline feature is external secrets management. Instead of leaving API keys sitting in plain text config files, you now have four dedicated commands: audit, configure, apply, and reload. This is especially important if you're running OpenClaw on a shared server or VPS. There are also four additional security fixes, including redaction of sensitive values in config outputs and rate limiting on voice endpoints. If you use OpenClaw in a language other than English, the memory embedding update is significant. Mistral is now a supported provider for memory embeddings, and seven languages including Spanish, Portuguese, Japanese, Korean, and Arabic now have proper semantic search support, meaning your agent can actually build meaningful context over time in your native language. For Discord and Telegram users, the ACP thread-bound agent improvements mean better lifecycle management, automatic reconnections, and no more message spam. Platform updates include native Synology NAS support, Android device notifications, and a new optional auto-updater. Before you update, check three breaking changes: tool failure replies now hide raw error details by default, DM scope defaults have changed, and legacy device off v1 has been removed. If you're on v1, migrate before updating.