OpenClaw v2026.5.25-beta.1 Release Summary

OpenClaw v2026.5.25-beta.1 introduces a series of targeted fixes aimed at enhancing the reliability of channel integrations—particularly iMessage—and streamlining the installation process across diverse operating systems. This release also addresses critical performance bottlenecks in Model Context Protocol (MCP) tool discovery and resolves routing issues for session-based model providers.

Key Changes

iMessage Stability and Integration

Several high-priority fixes have been implemented to resolve regressions and duplicate processing in the iMessage channel:

• Attachment Root Resolution: Fixed a regression where the image tool rejected valid iMessage attachments as path-not-allowed. The tool now correctly checks current channel/account inbound attachment roots through the existing inbound path policy, allowing files in ~/Library/Messages/Attachments to be read correctly (Fixes #30170).
• Watcher Deduplication: Resolved an issue where having both a default and a named account pointing to the same local Messages source caused duplicate imsg rpc processes. This previously led to duplicate inbound replies; the system now picks a canonical owner for the source, preventing redundant watchers (Fixes #65141).
• Catchup Cursor Persistence: Fixed a bug where iMessage catch-up could replay live-handled messages after a restart. The persisted catchup cursor now advances monotonically from the live inbound path, ensuring that messages processed before a restart are not re-dispatched (Fixes #85363).
• Slash Command Acknowledgements: Corrected the delivery of acknowledgements for authorized slash commands (e.g., /status, /new, /restart), ensuring they return to the source conversation.

Agent and Model Runtime Improvements

• MCP Tool Discovery: To prevent hung MCP servers from blocking session tool materialization, a 1500ms internal request cap has been added to tools/list catalog discovery. This replaces the previous 60s SDK default, allowing the system to degrade quickly when a server is unresponsive.
• Runtime Policy Matching: Fixed a critical routing failure where session entries with bare model IDs (missing the <provider>/ prefix) fell through runtime policy lookups. This previously caused requests to route to the wrong harness, often resulting in 404 errors and triggering auth profile cooldowns. The system now treats empty providers as "no constraint," allowing the entry's slash-prefix to be authoritative.
• OpenRouter Context Limits: The system now uses endpoint-specific context limits from top_provider metadata to prevent provider-routed models from overstating available context.

Installer and Cross-Platform Fixes

• Alpine Linux Support: The local-prefix CLI installer now uses Alpine's apk for Node.js, npm, and Git on musl Linux, avoiding incompatible glibc tarballs that caused node:sqlite failures.
• npm Freshness Bypass: Fixed a failure in the Unix installer where min-release-age configurations in .npmrc conflicted with the installer's --before flag. The installer now detects raw min-release-age settings to avoid mutually exclusive npm config combinations (Fixes #84743).
• Windows Compatibility: A variety of fixes were implemented to ensure Node package scripts, Vitest entrypoints, and credential helpers work correctly on native Windows paths, including the use of a cross-platform launcher for gateway and TUI entrypoints.

Impact

Users will notice significantly improved stability when using iMessage as a channel, with a marked reduction in duplicate replies and a fix for image attachment processing. Developers using MCP servers will see faster session startup times when dealing with unresponsive tools.

For those running OpenClaw on Alpine Linux or native Windows, the installation and testing workflows are now more robust. Additionally, users with complex npm configurations will find the hosted installer more reliable.

Upgrade Guide

iMessage Account Re-binding

Due to the watcher deduplication fix, if you previously had both a default and a named account targeting the same local backend, only one account (the named owner) will now be the active watcher.

• Action: If your agent bindings or status dashboards were pinned to the account that is no longer the active watcher, you should re-point those bindings to the new owner ID.
• Tip: Run openclaw doctor to see warnings regarding redundant accounts and receive guidance on which account ID now owns the source.