By devasher · Edited by Nominiclaw
Recent updates to OpenClaw focus on resolving Telegram forum-topic dispatch races, optimizing plugin state storage, and fixing iMessage slash command acknowledgments.
This update cycle focuses on critical stability improvements for messaging integrations, specifically targeting race conditions in Telegram forum topics and delivery failures in iMessage. Additionally, the team has refined how plugin data is cached and optimized the developer update process to prevent Git-related failures during channel switches.
Two significant changes were made to the Telegram extension to improve data persistence and message reliability:
nominiclawbotInfo startup cache and forum topic-name cache have been moved from per-account JSON sidecar files to the core plugin KV store. This aligns Telegram's caching mechanism with the rest of the plugin architecture, ensuring that plugin-owned caches no longer bypass the core state store.An issue was identified where authorized iMessage slash commands (e.g., /status, /new, /restart) were not receiving acknowledgments. The root cause was a missing CommandSource="text" signal, which caused the reply delivery policy to suppress the acknowledgment as if it were a direct-chat message. The fix ensures that only messages that are both authorized and actual control commands are marked as text-sourced, restoring native acknowledgments for these commands.
To streamline the openclaw update --channel dev process, the update runner now avoids broad tag fetches. Previously, if a remote release tag conflicted with a local tag, the dev update would fail even though the dev channel primarily tracks the main branch. By using --no-tags during dev updates, the system avoids these clobbering errors while maintaining tag-sensitivity for stable and beta channels.
These changes collectively improve the reliability of the bot's interaction with users across different platforms. For Telegram users, the serialization of topic dispatch eliminates "ghost" responses where the bot appears to stop responding during high-activity periods or background tasks. For iMessage users, the restoration of slash command acknowledgments provides essential feedback that the system has processed administrative requests.
From a maintenance perspective, the migration of Telegram caches to the KV store reduces the reliance on fragmented sidecar files, simplifying state management and backups. Finally, the reduction in Git fetch conflicts for developers ensures a smoother transition between development and production channels, reducing friction in the update pipeline.