OpenClaw Update: Enhancing Multi-Agent Orchestration and Channel Reliability

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.

Merged PRs

• fix(imessage): avoid visible media placeholder text Original PR
• Bootstrap agent sessions before send Original PR
• fix(imessage): make inbound image attachments readable by agents Original PR
• fix(openai): clarify remote Codex OAuth prompt Original PR
• fix(telegram): fall back to root groups on empty account allowlist Original PR
• [Fix] Add incremental chat delta payloads Original PR
• gateway: pass Talk session scope to resolver [AI] Original PR
• fix(test): isolate auth profile secrets in test state Original PR
• fix(sglang): preserve reasoning replay history Original PR
• fix: preserve managed plugin peer dependencies Original PR
• Fix Copilot Gemini image understanding Original PR
• Gate node surfaces on pairing approval Original PR
• fix(config): serialize concurrent config mutations Original PR
• fix(discord): suppress runaway bot-to-bot loops with per-pair sliding-window guard Original PR
• [codex] use in-process subagent announce handoff Original PR
• fix(telegram): limit startup getMe fanout Original PR
• Require approval for setup-code device pairing [AI] Original PR
• [AI-assisted] fix(docker): pin setup-time container paths Original PR
• feat: steer mid-turn prompts by default Original PR
• [AI-assisted] fix(ui): prevent chat actions overlapping replies Original PR
• [AI-assisted] fix(channel): refresh WeCom onboarding install Original PR

Key Changes

Core Infrastructure & Configuration

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.

Channel Reliability & Safety

• Discord Bot-to-Bot Guards: To prevent infinite "ping-pong" loops between bots when allowBots 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.
• Telegram Optimizations: The Telegram integration now limits concurrent 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.
• iMessage Enhancements: Inbound HEIC/HEIF photos are now automatically converted to JPEG via macOS 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.

Agent Orchestration & UX

• Mid-Turn Steering: The 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.
• Subagent Handoffs: Subagent completion announces now route through the in-process Gateway dispatcher rather than an RPC loopback, reducing latency and removing dependencies on the loopback transport for same-process handoffs.
• Chat Delta Payloads: The Gateway now provides optional additive deltaText in chat delta events, allowing clients to render incremental text chunks more stably without having to infer them from cumulative snapshots.

Impact

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.