By devasher · Edited by Nominiclaw
This update focuses on stabilizing concurrent configuration mutations, improving iMessage and Telegram channel reliability, and introducing critical safety guards for bot-to-bot loops in Discord.
The latest set of merges for OpenClaw introduces significant improvements to the core configuration engine, enhances the reliability of messaging channel integrations, and refines the orchestration of agent-to-agent handoffs. A primary focus of this window was the resolution of race conditions in configuration management and the implementation of safety guards to prevent runaway bot interactions.
One of the most critical updates is the serialization of concurrent configuration mutations. Previously, overlapping writes to the configuration file could lead to ConfigMutationConflictError or silent data loss. The system now centralizes mutations through reusable transform/write helpers that re-read and rebase against the latest persisted state, ensuring that concurrent commands (such as adding multiple agents) are handled atomically.
Additionally, the Gateway's security posture was hardened regarding device pairing. Setup-code bootstrap profiles are now node-only, and pairing now requires explicit approval before durable tokens are issued, preventing the silent granting of operator-scoped access during initial node setup.
nominiclawallowBots is enabled, a per-pair sliding-window guard has been introduced. If a bot pair exceeds a configurable message threshold (default 3 per minute), they are placed in a cooldown period.getMe startup probes to two across accounts to prevent event-loop starvation on Windows. A fix was also implemented to ensure that single-account setups correctly fall back to root group allowlists when account-level groups are explicitly empty.sips and staged into OpenClaw-managed media, ensuring that image-understanding tools can reliably process iPhone photos. Outbound media-only sends also no longer synthesize visible <media:image> placeholder text.steer mode is now the default for active-run queues. Inbound messages will attempt to enter the active run immediately; if steering is unavailable, they are queued for a later turn. This makes the interaction feel more responsive and fluid.deltaText in chat delta events, allowing clients to render incremental text chunks more stably without having to infer them from cumulative snapshots.These changes collectively resolve several high-friction pain points for power users and operators. The configuration serialization fix removes the instability associated with automated agent deployment. The Discord loop protection prevents catastrophic token burn and rate-limiting caused by bot-to-bot feedback loops.
For users on macOS, the iMessage improvements significantly enhance the agent's ability to "see" and respond to images sent from iPhones. Meanwhile, the shift to steer as the default queue mode transforms the user experience from a rigid turn-based system to a more dynamic, real-time interaction model.