By devasher · Edited by Nominiclaw
This beta release focuses on significant performance optimizations for the Gateway, enhanced voice and Talk mode capabilities, and critical stability fixes for iMessage, Telegram, and WhatsApp integrations.
OpenClaw v2026.5.26-beta.1 introduces a series of deep architectural optimizations to reduce latency and resource consumption:
nominiclawopenclaw doctor now uses read-only loads that skip unnecessary cloning. Additionally, session write lock acquisition now independently enforces maxHoldMs (default 5 minutes), preventing gateway freezes when large session files cause slow writes.node-llama-cpp teardown failures—particularly on Apple Silicon—do not crash the entire Gateway process.Realtime voice capabilities have been significantly expanded, particularly for mobile users:
Several production-ready improvements have been made to core messaging channels:
/command@BotName) as explicit mentions to satisfy requireMention gates.channels.imessage.dmHistoryLimit to provide context for fresh DM sessions.OPENCLAW_HOME for media paths, fixing silent failures in Docker deployments.personality: "none") to ensure OpenClaw workspace instructions remain authoritative. Turn timeouts are now kept strictly within the Codex runtime boundary to prevent poisoning shared app-server clients.createAgentToAgentPolicy wildcard matcher was replaced with a linear-time glob matcher to prevent Regular Expression Denial of Service (ReDoS) attacks.modelPatterns are now guarded with compileSafeRegex to reject unsafe patterns that could cause catastrophic backtracking.ENETDOWN errors during outbound connects caused the Gateway to exit and be parked by launchd.download-file results were accidentally included in auto-reply media, potentially re-uploading private attachments.--stack-size.mergeScopedSearchConfig injected legacy shapes that the validator subsequently rejected.New observability tools have been added to make failures easier to inspect:
diagnostics.otel.captureContent is enabled.channels.imessage.allowFrom is non-empty, the /approve text command is now authorized strictly against that list rather than the broader DM allowlist. Ensure all authorized approvers are listed in allowFrom.default and a named account targeting the same local Messages source, only the named account will now start a watcher. Inbound messages will be tagged with the named account's ID. Use openclaw doctor to identify redundant accounts and re-point your bindings if necessary.